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

[Bart Lateur]

On Wed, 30 Aug 2000 00:08:46 -0400, Stephen P. Potter wrote:

>Personally, I would say that q/.../ and friends were a bad idea.  A lot of
>non-gurus see /.../ (whatever comes before it) and their first impression
>is that it has something to do with regex.  I would suggest that anything
>that isn't a regex should not use /.../.

Sorry, the slashes are not part of the keyword. It is plain and simple
q, qq, qw. This works just as well:

        q#...#
        qq!...!
        qw{...}
        qw'...'

You're FREE to choose whatever delimiter (set) you want. I prefer to
pick something that stands out, and doesn't appear inside the string.
Slashes are just ONE possible choice.

You even don't need to attach the opening delimiter to the keyword;
Abigail uses this trick a lot to create obfuscated (= confusing) code.
See comp.lang.perl.misc.

        print q qWhat do you want?q;
-->
        What do you want?

-- 
        Bart.