Re: RFC 165: Allow variables in a tr///

Perl has always excelled at convenience.  Look at this code:

    while (<>) {
	for (split) {
	    s/foo/bar/g;
	    next if /glarch/i;
	    tr/aeiou/eioua/s;
	    print;
	} 
    } 

There is *nothing*wrong* with any of them, and to suggest breaking
them is extremely demoralizing.  Don't you people have anything
that's *broken* to fix?   Sheesh.

I fully expect to see an RFC for each and every lovely Perlism 
that isn't in C, Python, and Java.  Well, Perl *isn't* C, Python,
or Java, and there's no need to freak out just because of this!!

--tom