View Single Post
Old 12-05-2012, 10:00 PM   #48
SteveEisenberg
Wizard
SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.SteveEisenberg ought to be getting tired of karma fortunes by now.
 
Posts: 1,791
Karma: 12452388
Join Date: Jun 2008
Location: Philadelphia USA
Device: Kindle Keyboard 3G
Quote:
Originally Posted by teh603 View Post
Not like it resembles any modern programming language. You can't even manually number your lines anymore.
I just checked Visual Basic in Visual Studio 2012. You still can manually number executable lines. You (or the software you have do this for you) need to put a colon after the line number; otherwise, it works just about like in VB6.

The only reason I know that you might want to do something in this ballpark is if you have lots of originally pre-.NET code and don't have time to change it to structured error handling. One then can continue use of the Erl property to journalize the source code line generating an error. Structured error handling doesn't need those explicit line numbers because it journalizes based on the ones outside your code and optionally visible.

Now back to our regularly scheduled mobile reading web site.
SteveEisenberg is offline   Reply With Quote