On Mon, May 30, 2005 at 04:49:33PM +0100, dominic beesley wrote: > The "standard" is to have the byte after the BRK as an errorcode > followed by a NULL > terminated string. Makes for very compact code in the OS ROMS but can be > a pain in > the arse when writing code. I see. > A further thought on this... If I trap escape during OS functions (and > set a flag that is > checked on return) would this make Escape handling safer....? If I understood correctly, the vector is never called asynchronously, so the cc65 library is in a known state. This means that either solution is safe. But you'll probably need the longjmp anyway, since you cannot return from the BRK. Mapping the vector to an error code would make it similar to calls on other platforms, which could be an advantage. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Tue May 31 11:32:36 2005
This archive was generated by hypermail 2.1.8 : 2005-05-31 11:32:39 CEST