>For the record, the UTF8 version of tr/// does not use a plain 256K >table. It uses a data strcuture called a 'swash'; this is also the >data structure that is used by the UTF8 versions of 'uc' etc., the >\p{...} regex escapes, and the others. The swash is based on a hash, >and the code is in utf8.c. And is connected to a "swatch": /usr/local/src/perl/utf8.c:/* a "swash" is a swatch hash */ --tom
- Re: RFC 165 (v1) Allow Varibles in tr/// Nathan Wiger
- Re: RFC 165 (v1) Allow Varibles in tr/// Bryan C . Warnock
- Re: RFC 165 (v1) Allow Varibles in tr/// Bart Lateur
- Re: RFC 165 (v1) Allow Varibles in tr/// Mark-Jason Dominus
- Re: RFC 165 (v1) Allow Varibles in tr/// Stephen P. Potter
- Re: RFC 165 (v1) Allow Varibles in tr... Bart Lateur
- Re: RFC 165 (v1) Allow Varibles ... Bart Lateur
- Re: RFC 165 (v1) Allow Varibles ... Stephen P. Potter
- Re: RFC 165 (v1) Allow Varib... Mark-Jason Dominus
- Re: RFC 165 (v1) Allow Varib... Stephen P. Potter
- Re: RFC 165 (v1) Allow Varib... Tom Christiansen
- Re: RFC 165 (v1) Allow Varibles in tr... Tom Christiansen
- Re: RFC 165 (v1) Allow Varibles ... Stephen P. Potter
- Re: RFC 165 (v1) Allow Varib... Bart Lateur
- Re: RFC 165 (v1) Allow Varib... Tom Christiansen
- Re: RFC 165 (v1) Allow Varibles in tr... Jonathan Scott Duff
- Re: RFC 165 (v1) Allow Varibles in tr/// Chaim Frenkel
- Re: RFC 165 (v1) Allow Varibles in tr/// Mark-Jason Dominus