JDBP> I'm writing an interpreter "engine" for command scripts (a.k.a. "batch
files").
> The idea is that one can link CMDAPI.DLL into one's application and run
> command scripts and execute command lines in the context of the current
process
> much like one does with the REXX interpreter in REXXAPI.DLL.
JDBP> I've reached the stage where the engine executes command lines and runs
command
> scripts, and supports pretty much everything from environment variable
> expansion and internal commands to multiple commands on one line and
pipelines.
> I'm now looking for people to use and test the API in their programs.
JDBP> I can see a wide variety of uses for such an API, from NC clones and
YAOS
> variants that no longer need to "shell out" to run commands, to novel
> approaches to specliased command interpreter programs, such as NSLOOKUP
or an
> FTP client, giving them the scripting, redirection, environment variable
> expansion, and pipelining abilities that they so often lack because
their own
> interpreters are comparatively primitive. (The CMD interpreter, like
the REXX
> interpreter, is designed to be extensible. So an FTP client would
extend it by
> adding internal commands for "GET", "PUT", "LS", and the like, for
example.)
JDBP> If anyone is interested, please let me know immediately.
Johnathan, I'd be interested, but my current state of knowledge
of OS/2 programming (Expert DOS, so-so at Win32), might make for
a significant latency in useful feedback...probably not what you
are looking for.
But I'd be interested in taking a look anyways, just to see what
I can learn, and I'd certainly report any findings. Might even be
good to have a novice look at it from the understandability /
usability standpoints. If that's good enough for you then:
leea@psynet.net
Thanks,
LRA
-- SPEED 2.01 #2720: ... Win95: The "ValueJet" of software.
--- Platinum Xpress/Win/Wildcat5! v2.0
* Origin: Memory Alpha - (253) 859-6200 (1:343/311)
|