APL2 provides two methods for providing input to sessions: the -input and -sm piped invocation options.
All the data provided through these options is added to the stack during initialization.
The data is pulled off the stack one line at a time in response to APL2 interpreter input prompts.
It can be difficult to distinguish interpreter initialization data and application input passed through these options.
In addition, -sm piped prevents use of the session manager for interactive debugging.
Furthermore, when input is piped or the Runtime Library is used, APL2 terminates when the piped data is exhausted.
Therefore, there is no way to perform any processing after the input has been exhausted.
All these facts make it very difficult to develop and debug applications that use piped input.
When using the APL2 Runtime Library, all output is discarded, unless -sm piped is used.
When using the APL2 Runtime Library or -sm piped is used, the session manager is not available for interactive debugging.
These facts makes it very difficult to develop and debug applications that use piped output.
The Standard IO package solves all these problems and makes it easier to handle both piped input and output. The package's routines enable direct access to the input, output, and error streams. There is no interaction between the package's routines and the APL2 interpreter's stack or input and output mechanisms. You can even use the Standard IO routines when the session manager is active. Developing and debugging applications that use input and output streams is so much easier, you might actually want to try it!
This package only runs on Windows.
To download the Standard IO Tools, read the Tools Terms and Conditions, check the box below, and push the Download button.
I have read and agree to the Tools Terms and Conditions.
To purchase the Standard IO Tools, click here. The price is $50.
Back to Tools