Well, it wasn't the error tables I wanted. It was which statement in a line of basic caused the error. Launchpad's accessory programs are written in compiled BASIC and there are some multi-statement lines causing me problems. It would be useful to know the statement which caused the error rather than rewrite it all on separate lines.
I'm having problems with one of these programs running OK interpreted, but not when compiled. -- Dilwyn Jones ----- Original Message ----- From: Phoebus R. Dokos (Φοίβος Ρ. Ντόκος) <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 15, 2003 5:21 PM Subject: Re: [ql-users] error lines > > On Wed, 15 Oct 2003 12:22:32 +0100, Dilwyn Jones <[EMAIL PROTECTED]> > wrote: > > > > > Anyone know how to get the statement number within a line when an > > error occurs? > > > > Obviously, ROMs which support ERLIN return the line number. It would > > be helpful to get the statement number as well for debugging > > purposes - what I'd like is for my debugging routine to return > > something like: > > > > REPORT #channel > > PRINT #channel,'AT LINE ';ERLIN;':';error_statement > > > > It's probably stored in the basic variables area somewhere, though I > > can't seem to find it. > > > > -- > > Dilwyn Jones > > > > > > Isn't it REPORT supposed to show the Message tables? > > Phoebus > > > -- > Visit the QL-FAQ at: <http://www.dokos-gr.net/ql/faq/> (Still uploading > stuff!) > Visit the uQLX-win32 homepage at: <http://www.dokos-gr.net/ql/uqlx.html> > Visit the uQLX-mac home page at:<http://www.dokos-gr.net/ql/uqlxmac.html> >
