Ar an ceathrú lá de mí na Samhain, scríobh stephen(a)xemacs.org: 
 Aidan Kehoe writes:
 
  > The results are cached, but to get a result, XListFonts may be called
  > an insane number of times, often, as mentioned, with an entirely
  > inappropriate pattern for the given charset. This is as expected, and
  > can’t be avoided with regex charset-registry fields.
 
 Er, you seem to be forgetting that a disjunction of fixed strings *is*
 a regex.  Ie, your API "can't work" either.  
It can avoid the ‘entirely inappropriate pattern for the given charset’ 
aspect, and that is important. Remember that the existing API says nothing
about _where_ the charset-registry pattern matches; "courier" is an
appropriate value for it. 
  But it does, so I still think:
 
  >  > A working cache (with a switch to revert to old uncached behavior)
  >  > could be backported to 21.4, but I don't think an API change like
  >  > the one you've proposed should be. 
Agreed, I don’t propose backporting anything to 21.4. But my understanding
is that the cache works; the performance problems are a result of the design
being heinous, not any implementation bug. What makes you think the cache
doesn’t work, if that is your understanding? 
-- 
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta