Re: arg parsing

1999-10-04 Thread Mark B. Elrod
POSIX would be a plus but we still have to make sure that there are no spaces between args and their parameters so that we can distinguish what params are ours and what params are a random component. elrod [EMAIL PROTECTED] wrote: > On 4 Oct, Gabor Fleischer wrote: > >> freeamp -uitheme.ui -ui

Re: [Fwd: arg parsing]

1999-10-04 Thread robert
On 4 Oct, Gabor Fleischer wrote: >> freeamp -uitheme.ui -uilcdproc.ui blah.mp3 >> or this could be written >> freeamp -ui[theme.ui lcdproc.ui] blah.mp3 > Hmm. > freeamp --ui=theme,lcdproc blah.mp3 > > As I know the most POSIX-like is that we hawe "-X"-ish one letter > switches, orr "--WORD"-ish

Re: [Fwd: arg parsing]

1999-10-04 Thread Gabor Fleischer
> freeamp -uitheme.ui -uilcdproc.ui blah.mp3 > or this could be written > freeamp -ui[theme.ui lcdproc.ui] blah.mp3 Hmm. freeamp --ui=theme,lcdproc blah.mp3 As I know the most POSIX-like is that we hawe "-X"-ish one letter switches, orr "--WORD"-ish long arguments. Also POSIX sais, that "-u them

[Fwd: arg parsing]

1999-10-03 Thread Mark B. Elrod
so we want to allow for other components to accept args that we might ot know about. it looks like the current way we do things does not allow for us to really intelligently parse out args. for instance the current code would not know how to handle this: freeamp -someComponentArg someComponen