DAY 005: ERDEV$
#7
(11-10-2022, 07:32 AM)Pete Wrote: It's old school for providing the device specific status information after an error. I've never used it, but in an error trap, my guess is it was used to obtain comm port, maybe printer status, etc. when the process errored out.

Now can I get us that brown paper bag?

Pete

Speaking of brown paper bags, I sure wish they'd add a "try...catch" with stack trace, or in the very least the old "on error resume next" with err.number and err.description. Error handling is one thing which QB64 lacks that would make life easier.
Reply


Messages In This Thread
DAY 005: ERDEV$ - by SMcNeill - 11-10-2022, 06:04 AM
RE: DAY 005: ERDEV$ - by vince - 11-10-2022, 06:51 AM
RE: DAY 005: ERDEV$ - by Pete - 11-10-2022, 07:32 AM
RE: DAY 005: ERDEV$ - by madscijr - 11-11-2022, 12:21 AM
RE: DAY 005: ERDEV$ - by RhoSigma - 11-10-2022, 09:27 AM
RE: DAY 005: ERDEV$ - by madscijr - 11-11-2022, 12:20 AM
RE: DAY 005: ERDEV$ - by Pete - 11-10-2022, 09:33 AM
RE: DAY 005: ERDEV$ - by Pete - 11-11-2022, 12:33 AM



Users browsing this thread: 2 Guest(s)