>Personally, I would say that q/.../ and friends were a bad idea.
That's one opinion. As Piers points out, it's hardly universal.
Go read what I just wrote Uri.
>A lot of
>non-gurus
So what?
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 /.../. Make q, qq, etc use matched
>pairs.
Pick your own quotes is a perl thing. Let them learn this concept.
If they can't, you made a bad hiring choice.
>Make tr look like a regular function and do
>tr(SEARCH, REPLACE, MOD, STR). It just seems more orthagonal to me.
Transforming everything that's syntactically distinctive in Perl a
simple C-looking function will homogenize it into the same boring
sameness (and thence to illegibility) as the proverbial fingernail
clippings stranded in a bowl of oatmeal.
Don't even dream of it. This is part of what makes Perl, Perl, you know.
Not everything looks like an import from libc. And shoudn't.
--tom
