Rick Engebretson wrote:
CBFalconer wrote:
PascalP did that, but limited it to names mentioned within parentheses. I.E:
PROGRAM foo(alpha, beta, gamma, input, output) .... BEGIN .... END.
could be run with a command line explicitly using parentheses:
foo (file1, , file3)
and would access alpha, beta, gamma (assuming declared to be files) as the local files named file1, beta, file3. This only changed the default local ids attached to those files, and could still be over-ridden.
For detailed command line work the whole command line was available to the program as the one line text file named "cmd". So something like:
VAR cmd : text; BEGIN reset(cmd); (* The default id for a file is the Pascal name *) read(cmd, somewhere); ...
would gather the command line for programmatic parsing and usage. Redirection with < and > is stripped from the command line.
Thank you. Good starting point.
There are many shells out there now. I like and understand TCL. Perl and Python are popular, but I'm too old to learn them. Kurt Wall, in "Linux Programming by Example," describes pipes down to the kernel level.
So I'm picking up references, bit by bit.
Most of the details are available on my site, in:
http://cbfalconer.home.att.net/download/ppmanual.zip
and you can also find a MSDOS port of the compiler proper, but not the code generators. The binaries for all for CP/M are available in the download/cpm directory.