Dan Sugalski <[EMAIL PROTECTED]> wrote:
> On Thu, 13 Nov 2003, Leopold Toetsch wrote:

>> Dan. It starts with ascii keys, unicode code-points 0x00..0x7f.
>> When the first non-ascii key is to be stored, *ascii* keys are changed to
>> utf8.

> Which doesn't do much good if we've got non-ascii, non-unicode keys.

Whatever these are (PDDs?), they aren't handled with string_compare (or
string_eqal) either. Hash has since some time a pluggable interface for
the compare (and the hash_value) function. Such keys need a different
compare function.

I just would like to replace the current slow string_compare solution
with a faster equivalent.

>                                       Dan

leo

Reply via email to