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

> Note that the 256-byte thing is out the window with Unicode, but that
> I no longer know how it is done.

Thanks.  I was going to mention that, but I forgot before I sent the
message.  The 256-byte thing is still in place with unicode, but it's
only used on byte strings, not on UTF8 strings.  Since the byte/UTF8
thing might be going out the window in Perl 6, it's hard to speculate
about the implications for tr///.

But I think my main point still stands: We don't have any problem with
reconstructing a (potentially humongous) regex structure at run time,
so I don't see why we should have a problem with reconstructing the
tr/// tables at run time.