Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!samsung!olivea!mintaka!bloom-beacon!eru!hagbard!sunic!news.funet.fi!funic!polaris.utu.fi!polaris.utu.fi!sutela
From: sutela@polaris.utu.fi (Kari Sutela)
Newsgroups: comp.sys.amiga.tech
Subject: parseargs()/parseopts()
Message-ID: <1990Nov20.115248.19468@polaris.utu.fi>
Date: 20 Nov 90 11:52:48 GMT
Sender: sutela@polaris.utu.fi (Kari Sutela)
Organization: University of Turku, Finland
Lines: 22

I have seen several references to a parseargs() or parseopts() function
(for example, Peter da Silva's) on this newsgroup. I'm wondering if someone
has really implemented this function (or at least, is working on one) or
is its existence just wishful thinking.

On a related note, I found a problem in Aztec C's cliparse() function which
might make getargs() infeasible (with Aztec C, at least). Aztec C's cliparse()
strips ALL quotes from the command string even if the quoted string was a
single word. Thus, a LIST-like command would never be able to tell the
difference between 'LIST FILES' and 'LIST "FILES"'.

To be exact, all quotes are not stripped---for examples, I tried something
like 'LIST ""FILES""' but the result was even worse. If I recall correctly
""FILES"" would be broken into two tokens: the first would be an empty token
(from the first pair of quotes) and the other would contain 'FILES"'. Clearly,
Aztec's cliparse() is broken and a replacement should be written. I have
tested this on version 5.0b --- before I report this bug or feature to Manx
I'd like to know if it behaves similarly in version 5.0d. BTW, how does
SAS C handle these situations?

-- 
Kari Sutela	sutela@polaris.utu.fi