I was all set to integrate the \N{...} support into the Unicode-escape
encoding, and dynamically load the hash table data in on demand, but
dynload_aix only cares about module entry points and won't let you specify
an explicit function name.
Ugh. So, its question and answer time folks:
1) If we can't dynamically load the hash table data, is it that big of
a deal?
Probably only for WinCE, palm pilot, etc, and they already
have patches against CVS.
2) Or, should I just have a separate encoding?
I'd prefer to pick option #1 since Perl natively supports the syntax in
their strings. The data is all constant read/only data that will be mmapped
directly from the binary, so it only effects working set if the feature is
used.
Barry, Greg, Guido?
The only feedback I got last time I submitted the patch was from MAL, it'd
help if some other folks would comment on it.
Thanks,
Bill
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