Oops. My mistake. The $SEARCH() call avoidance
I had in mind only works if the @ARGV element contains
a $SEARCH() wildcard. On VMS that means the * character,
the % character (which acts as ? does on a typical
unix shell), or the ... set of three characters. Hence
these give what you wanted, albeit with the extra
character(s) embedded:
$ perl -wle "print [EMAIL PROTECTED]" """<foo*>"""
<foo*>
$ perl -wle "print [EMAIL PROTECTED]" """<%foo>"""
<%foo>
$ perl -wle "print [EMAIL PROTECTED]" """<fo...o>"""
<fo...o>
I am not sure what you want to do with it but
perhaps something along the lines of Alan's
special escape sequence could be made out of one
of those (?).
Peter Prymmer
Michael G
Schwern To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc: [EMAIL PROTECTED], [EMAIL
PROTECTED]
om>
Subject: Re: Quoting < on the command
line.
03/29/2003 06:41
AM
On Sat, Mar 29, 2003 at 06:26:50AM -0500, [EMAIL PROTECTED] wrote:
> Does this work as required?
>
> $ perl -wle "print [EMAIL PROTECTED]" """<foo>"""
>
> I expect that might work only with a very recent perl 5.8.1
> candidate (e.g. [EMAIL PROTECTED] or later).
With 5.8.0:
$ perl -wle "print [EMAIL PROTECTED]" """<foo>"""
"<foo>"
--
We don't know. But if we did, we wouldn't tell you.
