-Original Message-
> From: Paul "Bo" Peaslee [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, March 26, 2002 11:02 AM
> To: win32-users-listserv
> Subject: One-liners
>
> While reading the recent article, "Perl One-liners", from The Perl Review;
> I
&
Paul \"Bo\" Peaslee wrote:
> While reading the recent article, "Perl One-liners", from The Perl Review; I
> decided to follow along. Didn't take too long before I realized I couldn't
> do them on Windows (NT) as written. The command line doesn't
> perl -e 'print "Hello World!\n"'
> "Can't find string terminator "'" anywhere before EOF at -e line 1."
> Question is - How does anyone do substantive one-liners in Windows?
perl -e "print qq{Hello World!\n}"
--
Simon Ol
While reading the recent article, "Perl One-liners", from The Perl Review; I
decided to follow along. Didn't take too long before I realized I couldn't
do them on Windows (NT) as written. The command line doesn't like Perl
script enclosed in single quotes. For example:
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 28, 2001 2:57 PM
Subject: One-liners on wildcarded files in Win32?
> From: Matthew Daly
>
> In chapter 20 of Lemay's book, she gives the following example
of
e at ActiveState, so I have no idea where it is
>
> Giovanni Zezza wrote:
>
>
> >>3) I hope this doesn't sound ill-tempered, but why do some of you
> >>respond with one-liners like "perldoc -q perllocale" or the like?
> >>
> >>An
"Ted S." wrote:
>
> Oh really? I tried it and got three error messages each time all of which are the
>same saying:
>
> Can't spawn "command.com": No such file or directory at c:\PERL\BIN/perldoc.bat line
>383.
>
> I hope I've got everything right, since I had to retype it by hand, not being
