> 2. We pass the signal on to the user and let them perform > their own termination processing. > > Number 2 can lead to big problems because of the console I/O > issues. But if we disable console I/O how do we process > console input if the user performs a CHARIN or a LINEIN > function? Anything we give back to the user will lead to > inappropriate results because the script can not determine > whether the terminal is gone away or not. Was the input from > a real user or something else? > > I do not think we can come up with a simple solution to > choice number 2. > So let's not go there at all.
I don't follow -- these cases must already be handled if a script is started without a terminal or if it goes away. TRL, for LINEIN for example, says: If a complete line is not available in the stream, then execution of the program will normally stop until the line is complete. If, however, it is impossible for a line to be completed due to an error or other problem then the NOTREADY condition is raised (see page 142) and LINEIN will return with whatever characters are available. So it is well-defined, I think. 'no terminal' is surely an "error or other problem". Mike ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
