 |  |  |  |  |  |  |  |
Perl error reports: error prone
 |
•
•
Join Date: Jun 2006
Posts: 263
Reputation: 
Solved Threads: 1
Posting Whiz in Training
I was wondering whether anyone else has experienced this. When a script I am working on got above a certain size, the line numbers quoted in the compile and run time error messages started to be inaccurate. The line numbers now seem to always be before where the error actually is. I've seen this so many times now it can't be my imagination. Has anyone else seen this happen?
Steven.
Steven.
The one question you should not ask when teaching a new language structure is "Do you understand?". Do you understand?
•
•
Join Date: Oct 2006
Posts: 262
Reputation:
Solved Threads: 22
Posting Whiz in Training
Depends on what the error it is.
It is very important to read this: http://www.catb.org/~esr/faqs/smart-questions.html
|
Similar Threads
- Dev-C++ - [Build Error] [main.o] Error 1 (C++)
- Parse error: syntax error, unexpected T_STRING (PHP)
- Parse error: parse error, unexpected T_STRING (PHP)
- PHP Parse error: parse error, unexpected T_STRING (PHP)
- Parse error: parse error, unexpected T_STRING in /home/thei2k9/public_html/includes/f (PHP)
- iexplorer.exe send error reports(1 too many) (Web Browsers)
Other Threads in the Perl Forum
- Previous Thread: Odd string concatenation behavior?
- Next Thread: "use" statement inside an eval: problem?
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest Perl Posts
- Today's Posts
- Unanswered Threads
