[Coco] signal/intercept routine in Basic09

[Wayne Campbell]

This sounds like a modification to the way drivewire sends signals?

Wayne

----- Original Message ----- 
From: "Robert Gault" <robert.gault at worldnet.att.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, January 23, 2010 5:52 PM
Subject: Re: [Coco] signal/intercept routine in Basic09


> Aaron Wolfe wrote:
>> It's probably worth noting that the "port closed" signal is not a part
>> of standard OS-9, it is a feature of the DriveWire additions we're
>> working on.  The signal's value is 4.  It is sent to a process when
>> the remote end of a TCPIP connection closes.
>>
>
> For what it is worth, Basic09 would trap the error 4.
>  ON ERROR GOTO 100
>  ERROR 4
>  END
> 100 PRINT"The error was caught."
>
> When this is run, the message is printed. Now the manual indicates that 
> there is no real difference between signals and errors. Errors are just 
> specific signals. So, if the signal to be caught is coming from Drivewire, 
> it does not seem to be getting through to Basic09. That's assuming error 
> trapping as above is being used.
>
> It may mean that using syscall to set up an intercept may not work either.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco