On Tue, 29 Aug 2000 20:36:46 -0400, Bryan C.Warnock wrote: >> The way tr/// works is that a 256-byte table is constructed at compile >> time that say for each input character what output character is > >Speaking of which, what's going to happen when there are more than 256 >values to map? A bigger table. For 16-bit characters, you'd need 2 x 64k = a 128k bytes table. Well, in principle. -- Bart.
- RFC 165 (v1) Allow Varibles in tr/// Perl6 RFC Librarian
- Re: RFC 165 (v1) Allow Varibles in tr/// Mark-Jason Dominus
- Re: RFC 165 (v1) Allow Varibles in tr/// Nathan Wiger
- Re: RFC 165 (v1) Allow Varibles in tr/// Mark-Jason Dominus
- Re: RFC 165 (v1) Allow Varibles in tr/// Tom Christiansen
- 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 ... Bart Lateur
- Re: RFC 165 (v1) Allow Varib... Bart Lateur
- Re: RFC 165 (v1) Allow Varib... Stephen P. Potter
- Re: RFC 165 (v1) Allow V... Mark-Jason Dominus
- Re: RFC 165 (v1) Allow V... Stephen P. Potter
- Re: RFC 165 (v1) Allow V... Tom Christiansen
- Re: RFC 165 (v1) Allow Varibles ... Tom Christiansen
- Re: RFC 165 (v1) Allow Varib... Stephen P. Potter