Re: Phantom Line Numbers

2003-01-07 Thread _brian_d_foy
In article [EMAIL PROTECTED], Christopher D . Lewis [EMAIL PROTECTED] wrote: On Monday, January 6, 2003, at 06:39 PM, Andy Lester wrote: syntax error at ./nudice-01c line 187, near sub displayResults syntax error at ./nudice-01c line 305, near sub rollRequest The problem is, you see,

Phantom Line Numbers

2003-01-07 Thread Christopher D . Lewis
I'm writing a little toy tool to teach myself more Perl than I have used before, and I am puzzled by error messages I get when trying to run and debug it: syntax error at ./nudice-01c line 187, near sub displayResults syntax error at ./nudice-01c line 305, near sub rollRequest syntax error at

Re: Debugging Problem: Phantom line numbers!

2003-01-07 Thread Christopher D . Lewis
On Tuesday, January 7, 2003, at 10:31 AM, Peter Scott wrote: [EMAIL PROTECTED] (Christopher D . Lewis) writes: My problem is that the errors Perl coughs up end with: syntax error at ./nudice-01c line 187, near sub displayResults syntax error at ./nudice-01c line 305, near sub rollRequest

Phantom Line Numbers

2003-01-06 Thread Christopher D . Lewis
I'm writing a little toy tool to teach myself more Perl than I have used before, and I am puzzled by error messages I get when trying to run and debug it: syntax error at ./nudice-01c line 187, near sub displayResults syntax error at ./nudice-01c line 305, near sub rollRequest syntax error at

Re: Phantom Line Numbers

2003-01-06 Thread Trey Harris
In a message dated Mon, 6 Jan 2003, Christopher D. Lewis writes: Any ideas how I debug lines which don't exist? Any ideas why Perl is reporting nonexistent line numbers? Perl 5.8.0. What modules are you using? If you're using any source filters, line numbers will be incorrect. Trey --

Re: Phantom Line Numbers

2003-01-06 Thread Andy Lester
syntax error at ./nudice-01c line 187, near sub displayResults syntax error at ./nudice-01c line 305, near sub rollRequest The problem is, you see, that (according to two different text editors) nudice-01c has only 304 lines Line numbers aside, you can find sub rollRequest, cancha?

Re: Phantom Line Numbers

2003-01-06 Thread drieux
On Monday, Jan 6, 2003, at 15:34 US/Pacific, Christopher D. Lewis wrote: I'm writing a little toy tool to teach myself more Perl than I have used before, and I am puzzled by error messages I get when trying to run and debug it: syntax error at ./nudice-01c line 187, near sub displayResults

Re: Phantom Line Numbers

2003-01-06 Thread Christopher D . Lewis
On Monday, January 6, 2003, at 06:39 PM, Andy Lester wrote: syntax error at ./nudice-01c line 187, near sub displayResults syntax error at ./nudice-01c line 305, near sub rollRequest The problem is, you see, that (according to two different text editors) nudice-01c has only 304 lines

Re: Phantom Line Numbers

2003-01-06 Thread Ken Williams
On Monday, January 6, 2003, at 06:49 PM, Christopher D. Lewis wrote: displayResults begins on 130 and goes to 187, though several intended features are not actually implemented yet -- I just wanted to see what I needed to do to get it running. I was able to eliminate several compile errors,

Re: Phantom Line Numbers

2003-01-06 Thread drieux
On Monday, Jan 6, 2003, at 18:01 US/Pacific, Ken Williams wrote: On Monday, January 6, 2003, at 06:49 PM, Christopher D. Lewis wrote: displayResults begins on 130 and goes to 187, though several intended features are not actually implemented yet -- I just wanted to see what I needed to do to

Re: Phantom Line Numbers

2003-01-06 Thread Chris Devers
On Mon, 6 Jan 2003, Christopher D. Lewis wrote: I was able to eliminate several compile errors, but got stuck when the errors stopped giving me clues I knew how to follow. Are you running with warnings strict mode? #!/usr/bin/perl -w use strict; # . That might make the

Re: Phantom Line Numbers

2003-01-06 Thread Chris Devers
On Mon, 6 Jan 2003, Chris Devers wrote: Are you running with warnings strict mode? And the other thing, which I forgot to mention, is that if you can narrow down the broken region of your script still can't figure it out, by all means send that code the errors it produces to the list for