Re: RFC 165 (v1) Allow Varibles in tr///

[Bryan C . Warnock]

On Tue, 29 Aug 2000, Mark-Jason Dominus wrote:
> I think the reason this hasn't been done before it because it's *not*
> quite straightforward.
> 
> 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?

 -- 
Bryan C. Warnock
([EMAIL PROTECTED])