Hi,
Yes I understand, I mean does not interpret doe's not executes user
defined actions then parses command line. May be I wrong, but I don't see
any interface for this.
It is not very priority. I can do it myself in my application like in this
pseudo language:
Loop option in AllOptions
HI,
Yes it is not very good idea and can be useful only for trivial situations.
At 07:06 AM 1/29/2002 -0800, you wrote:
Well,
With the handler approach CLI would become a kind of
command controller/dispacher. Is it what we shoot for?
If you have a way to specify a handler for an option
what
Hi,
What do you mean by CLI does not interpret cmd?
Now for the option types let me see what we could
imagine to have a complete list:
1. -a, --aaa - no additional argument needed
2. -a xxx, -aaa xxx - additional argument needed
3. xxx - only argument
All of those should be either required or
On Tue, 29 Jan 2002, Slawek Zachcial wrote:
Hi,
What do you mean by CLI does not interpret cmd?
I assume the equivelent of:
cvs -dfoo commit
He'd like to bind 'commit' (the cmd) to a particular
Command callback, or similar. Personally, I like
the idea, and have implemented
