Non-numeric ERL's in Next PB for DOS Version?

[Mike Luther]

Heck, why not just ask?

Any chance we can have an ERL return that will return not just
numeric line labels but TEXT-type labels too?

Inquiring mind wants to know!

Thanks.

------------------
Mike Luther
mike.luth[email protected]

[Mel Bishop]

Personally, I don't care about line numbers/labels. I use the
ERADR to go straight to the line that caused the error.


------------------

[Mike Luther]

Mel ..

I'm curious. Does ERADR survive RESUME? Could I tag it like I'm
doing the ERR and ERL and carry that to my error reporting file that
is generated by each application. That in an attempt to get where
we are going.

I've never pretended to be the smartest dog in the pound!


------------------
Mike Luther
[email protected]

[Michael Mattias]

I'm curious. Does ERADR survive RESUME?

Don't know, but I'll bet....

 ON ERROR GOTO ErrorTrap
 ...
ErrorTrap:
 My_Err   = ERR
 MY_ERADR = ERADR
 CALL AppendErrorInfoToFile (My_Err, My_Eradr, ErrFile$)
 RESUME whatever

.. would.

MCM

[Mel Bishop]

Originally posted by Michael Mattias:

 ON ERROR GOTO ErrorTrap
 ...
ErrorTrap:
 My_Err   = ERR
 MY_ERADR = ERADR
 CALL AppendErrorInfoToFile (My_Err, My_Eradr, ErrFile$)
 RESUME whatever

Good way of going. To expand on this:

 ON ERROR GOTO ErrorTrap
 ...
ErrorTrap:
 My_Err   = ERR
 MY_ERADR = ERADR
 CALL AppendErrorInfoToFile (My_Err, My_Eradr, ErrFile$)
 [b]
 if my_err = 58 then RESUME whatever     ' file already exists
 if my_err = 53 then resume whateverelse ' file not found
 resume someplaceelse or END             ' Specific error not listed
 [/b]

------------------




[This message has been edited by Mel Bishop (edited October 31, 2002).]

[Tom Hanlin]

Any chance we can have an ERL return that will return not just
numeric line labels but TEXT-type labels too?

I'll put it on the wish list. It may be that a TRY..CATCH design
is more likely, though, considering recent directions in PB/CC 3
and PB/Win 7.

------------------
Tom Hanlin
PowerBASIC Staff