In message <[EMAIL PROTECTED]>, Sally
<[EMAIL PROTECTED]> writes
>Why don't you work on the ones you can see, then the list will shrink, and
>you'll get rid of the errors eventually. I know that's not the point but it
>is a solution.
This is not I think likely to help as most of the errors are
consequential on the original "real " error, but thanks for the thought.
>
>
>-----Original Message-----
>From: james crease [mailto:[EMAIL PROTECTED]]
>Sent: 21 June 2001 09:26
>To: [EMAIL PROTECTED]
>Subject: Re: compilation errors in win98
>
>
>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
--
james crease
http://wocediu.org Tel. +1 302 645 4240
http://www.codata.org Tel. +44 1608 642335
