The problem is that the error messages are going to stderr instead of
stdout. The standard DOS shell (command.com or cmd.exe depending on
your system) doesn't understand how to capture stderr. The solution is
to get a better shell. Cygnus (now RedHat) makes cygwin a complete unix
style development enviroment for Windows boxen that includes the best
command shell available (IMHO): bash
(http://sources.redhat.com/cygwin/). I have also heard that 4dos gives
you the ability to capture stderr, but have never used their product
myself (http://www.jpsoft.com/). There are almost certainly other
packages out there.
On 21 Jun 2001 09:26:28 +0100, james crease wrote:
> Thanks I had tried that already and doesn't seem to work at compile
> time:-(
>
> In message <00e401c0f9cc$02ee7340$0901a8c0@profit>, Jos I. Boumans
> <[EMAIL PROTECTED]> writes
> >try capturing the output:
> >
> >perl foo.pl > outputfile.txt
> >
> >all that perl spits out should be in the outputfile.txt then
> >
> >regards,
> >
> >Jos Boumans
> >
> >----- Original Message -----
> >From: "james crease" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Sent: Wednesday, June 20, 2001 10:49 PM
> >Subject: compilation errors in win98
> >
> >
> >> I have a perl script which generates many compilation errors which
> >> scroll off the DOS window perl is running in. How do I capture (or
> >> recover) the lines that have scrolled away?
> >> --
> >> james crease
> >>
> >>
>
> --
> james crease
> http://wocediu.org Tel. +1 302 645 4240
> http://www.codata.org Tel. +44 1608 642335
>
--
Today is Boomtime, the 26th day of Confusion in the YOLD 3167
Keep the Lasagna flying!
