First things first - what is it going to be doing? Is it a small and quick
drop-in for command.com? Or a heavyweight replacement that does a lot more
things that command.com couldn't do? Decide that first.
Secondly, if you know about BNF, lex and yacc, it might be a good idea to do a
lot of
Some added comments...
Secondly, if you know about BNF, lex and yacc
Those are about parsing. In other words, they are about how
you decide what a STRING like copy *.txt *.com x: /z wants
to TELL your shell ;-).
What programming language you use is entirely up to you - though I doubt that
I
Some time ago I spent some time thinking about shells...
One approach that solves more problems is:
1) a .BAT allocates some environment variable with a lot of space, like
NEXTCMD=1234567890123456789012345678901234567(127chars)
2) the .BAT calls a program that can be written in any language,
