On Thu, Jul 06, 2000 at 06:28:12PM +0200, M.-A. Lemburg wrote: >... > Previously, Unicode used UTF-8 as basis for calculating the > hash value (the Unicode object created a UTF-8 string object > and delegated the hash value calculation to it, caching the > result and the string for future use). Since I would like > to make the internal encoding cache use the default encoding > instead, I have two problems to solve: Woah... are you saing that the "t#" marker could now return arbitrary encodings? That C code cannot depend on any particular encoding? Why? This is a pretty big semantic change. Cheers, -g -- Greg Stein, http://www.lyra.org/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4