Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!sdd.hp.com!usc!julius.cs.uiuc.edu!psuvax1!psuvm!cunyvm!uupsi!sunic!fuug!funic!polaris.utu.fi!polaris.utu.fi!sutela
From: sutela@polaris.utu.fi (Kari Sutela)
Newsgroups: comp.sys.amiga.tech
Subject: An alternative _cliparse() for Aztec C posted + questions
Message-ID: <1991Jan7.125631.3541@polaris.utu.fi>
Date: 7 Jan 91 12:56:31 GMT
Sender: sutela@polaris.utu.fi (Kari Sutela)
Organization: University of Turku, Finland
Lines: 22

I just posted my version of cliparse.c to alt.sources.amiga. I hope
it reaches the other side of the pond, too. Here's the blurb:

This is my version of the _cliparse() function for the Aztec C compiler.
You need the original cliparse.c from the 5.0 distribution diskettes and
the patch program to extract a working version.

This version properly supports quoted tokens and preprocesses the escaped
characters inside quoted tokens.

[end of blurb]

Actually, I have a question about the standard escape sequences. I have
never found a complete list of them and am assuming that the standard
sequences are: "**", "*"", "*e", "*E", "*n" and "*N". Have I missed any?

There's also an assumption which I had to make (I had to write around a
`feature' in some Manx-compiled programs, for example, Make). I'm assuming
that the last character on the supplied command line is always a newline.
Is this true for OS 2.0? How about program launches in SAS-compiled programs?
--
Kari Sutela	sutela@polaris.utu.fi