On Fri, May 07, 2004 at 10:13:13AM +0200, Leopold Toetsch wrote: : Or better create a string_equal_cstring. We are comparing : signatures here, which are just plain ASCII strings. I don't think, that : we should allow non-ASCII signatures.
[I'm assuming that these internal signatures contain actual type names and/or other identifiers. If that's not the case, please ignore this message.] I suspect we'll need to allow non-ASCII characters in signatures for those languages that support Unicode in identifiers (such as Perl). Fortunately, that does not imply that you have to make them full-fledged strings. if you force the encoding to normalized UTF-8, you can still use the low level compare as if it were ASCII, so it's probably okay to pretend it's ASCII for now. After all, that's why UTF-8 was designed to be a "super ASCII" in the first place... I think it'd be much better to switch to forced UTF-8 than to reinvent some other ASCII-based name mangling scheme to do the same thing. Larry
