Board index » off-topic » Visual basic line numbers vs. error parser (hopefully formatted better)
Mike
Delphi Developer |
Visual basic line numbers vs. error parser (hopefully formatted better)2004-01-21 12:22:06 AM off-topic3 Visual Basic 6 CW 6.5 When compiling Visual Basic from the command line within CW, the error line number returned by Visual Basic is the line number referenced from the strat of that portion of the source file that is normally accessible to the programmer in the Visual Basic IDE. (There is a lot of control definition code in form modules that preceeds this point, and is hidden from the programmer in the IDE.) However, CW uses the error number to position the cursor relative to the first physical line the source file, which is not line that has the error. If I take the line number where the control stuff ends and add it to the line number in the error file, I'm exactly on the line that actually has the error. Either CW should add the number of lines consumed by the control definition code to the error line number for purposes of positioning the cursor, or Visual Basic should be able to report the absolute error line. I've explored both options with no success. Any ideas on how I can handle this and automatically get positioned to the correct line when an error occurs? Thanks, Mike . |