> > > Besides, the Unicode object will have a buffer containing the > > > <default encoding> representation of the object, which, if all goes > > > well, will always hold the UTF-8 value. > > > > <rant> > > > > over my dead body, that one... > > Such a buffer is needed to implement "s" and "s#" argument > parsing. It's a simple requirement to support those two > parsing markers -- there's not much to argue about, really... why? I don't understand why "s" and "s#" has to deal with encoding issues at all... > unless, of course, you want to give up Unicode object support > for all APIs using these parsers. hmm. maybe that's exactly what I want... </F>
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