On Wed, Aug 30, 2000 at 12:31:24AM -0400, Stephen P. Potter wrote:
> Lightning flashed, thunder crashed and Mark-Jason Dominus <[EMAIL PROTECTED]> whis
> pered:
> | > > 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?
> |
> | It's already happened, but I forget the details.
>
> Let me see if I understand this correctly. For every tr/// in a program,
> 256 bytes have to be allocated? Even if I only do something like tr/a/A/?
> And, it is going to get worse for UTF8/UTF16?
Not necessarily. There are methods of compression through an extra
indirection that would only use 256 bytes if you were actually
transliterating the entire character set. The same goes for
UTF{whatever}.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
