[Coco] Error codes on SECB

[Mark Mellor]

Thanks, I realized after I sent the email that the ECB part probably stands
for Extended Color Basic.  Anyway, it looks like you have solved the
mystery.

Mark

----- Original Message ----- 
From: "William Astle" <lost at l-w.ca>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Friday, November 17, 2006 10:45 PM
Subject: Re: [Coco] Error codes on SECB


> Mark Mellor wrote:
> > What does SECB stand for?  In my book it says "File not found" for the
NE
> > error but it looks like you already know that with your sample code.
>
> SECB=Super Extended Color Basic
>
> That is, "Extended Basic 2.0" from a CoCo3.
>
> >
> > Mark
> >
> > ----- Original Message ----- 
> > From: "Diego Barizo" <diegoba at adinet.com.uy>
> > To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> > Sent: Friday, November 17, 2006 9:07 PM
> > Subject: Re: [Coco] Error codes on SECB
> >
> >
> >> I checked on the "Quick reference guide" and the NE error is not
listed.
> >> Also, this short program gives no number
> >> 10  ON ERR GOTO 1000
> >> 20 LOAD"PPPP"
> >> 30 STOP
> >> 1000 ? ERNO,ERLIN
> >> 1010 END
> >>
> >> If I change line 20 for WOAD "PP" I get the expected results for an SN
> > error
> >> BUT... If after the first program ends, I type ? ERNO, I do get 26 as
> >> answer... :-/
> >>
> >>
> >>
> >> William Astle wrote:
> >>> Diego Barizo wrote:
> >>>
> >>>> While debugging a program, I noticed that some errors just don't
> >>>> generate an error code, like "NE error"
> >>>> Is there anywhere I could "peek" to identify this error?
> >>>>
> >>>> And out of curiosity, does anyone know why some errors are not
> > included?
> >>>> ( I seen to remember another error that did not generate an error
code,
> >>>> but just can't remember which one)
> >>>>
> >>> I thought NE was error code 26 (Unravelled book confirms.)
Interestingly
> >>> enough, NE is defined by Extended Basic even though most folks would
> >>> only encounter it when using Disk Basic.
> >>>
> >>> Unless you're doing something odd, all errors go through the same
> >>> handling process so ERRNO should provide the error code (assuming ON
ERR
> >>> GOTO in effect). The only special handling I see in the error routines
> >>> is for some weird case of a UL error. (Note that if you aren't doing
ON
> >>> ERR GOTO, you won't get the error code stored anywhere.)
> >>>
> >>>
> >>
> >> -- 
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> http://five.pairlist.net/mailman/listinfo/coco
> >
> >
>
>
> -- 
> William Astle
> finger lost at l-w.ca for further information
>
> Geek Code V3.12: GCS/M/S d- s+:+ !a C++ UL++++$ P++ L+++ !E W++ !N w---
> !D !M PS PE V-- Y+ PGP t+@ 5++ X !R tv+@ b+++@ !DI D? G e++ h+ y?
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco