|
From: | Peter Teeson |
Subject: | Re: [Bug-apl] Command::process_line breakup |
Date: | Thu, 05 Jun 2014 13:38:58 -0400 |
Well this is an opportunity to bring up something that has been on my mind for some time. My feeling is that a better way to deal with the I/O issue is to have an abstract Class ( or Classes) from which the various I/O implementations can inherit. e.g. Class Input, Class Output or Class InputOutPut. The present implementation of a terminal / command line interface would be the default and be one example. In Xcode I have run into issues trying to make a simple wrapper for GNU APL. Not the least of these is avoiding terminal control codes which I presently do with apl launch options - a bit crufty. Mentally I have a picture of the interpreter as a (potentially) embeddable item with a full duplex I/O channel. It is the interpreter that is the crucial thing that does the work of solving. The I/O is just the Microphone and Speaker. Then one can use (or implement) the I/O mechanism of one's choice. Of course there must be constraints on what is acceptable input (must be characters and must be in quadAV?). I submit that this approach is preferable versus adding special case code (which is never ending) and IMHO neither elegant nor desirable even if it is practical. :-} Just my 2¢ FWIW. much respect to everyone. Peter On 2014-06-05, at 10:49 AM, Elias Mårtenson <address@hidden> wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |