Hi,
>> remember me? ;-)
>
>I sure do!
;-)
>> In the meantime I learnt why: POSIX ranges are always in ASCII order,
>> so [A-Z] won’t match any nōn-letters even on EBCDIC systems.
>
>Interesting! So POSIX assumes ASCII, to a certain extent.
Yes, it does. I think EBCDIC as charset is actually nonconformant,
but it probably pays off to stay close nevertheless. (This is
actually about the POSIX/'C' locale; other locales can pretty much
do whatever they want.)
>Even if you really do need a table, you could populate it on startup
>using these.
Indeed… but we have the compile-time translated characters all over
the source (I think we agreed earlier that not supporting changing
it at runtime was okay).
>> that won’t work in utf8-mode either anyway).
>
>I guess multi-byte is trickier... EBCDIC does have the
It definitely is, but I’ll reserve changing stuff there for later.
>Anyway, if you need any z/OS testing, feel free to drop me a line ;)
Thanks!
I hope to be able to get back to that offer eventually. Glad to
know you’re still interested after two years.
Goodnight,
//mirabilos
--
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
-- Thomas E. Dickey on the Lynx mailing list, about OpenSSL
