Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!ames!pasteur!ucbvax!unisoft!gethen!bdt!david
From: david@bdt.UUCP (David Beckemeyer)
Newsgroups: comp.sys.atari.st
Subject: Re: gcc problems
Message-ID: <381@bdt.UUCP>
Date: 12 Sep 88 20:12:34 GMT
References: <19880906162643.1.JRD@MOA.SCRC.Symbolics.COM>
Reply-To: david@bdt.UUCP (David Beckemeyer)
Organization: Beckemeyer Development Tools, Oakland, CA
Lines: 26

In article <19880906162643.1.JRD@MOA.SCRC.Symbolics.COM> jrd@STONY-BROOK.SCRC.SYMBOLICS.COM (John R. Dunning) writes:
>    Since can't run it I can't be of much immediate assistance.  Does
>    anyone here have suggestions?  My guess is the MT C shell does command
>    line arguments differently than gulam (the shell used by the guy who
>    did the port).  
>
>Yes, I'd guess that's true, but it's still a bit mysterious how it could
>get as confused as he describes.  Could it be that MT upcases command
>lines before executing them?
>
Perhaps others are interested too, so I'm posting this to help clear it up.
MT C-Shell V1.10 or higher and Micro C-Shell 2.70 and higher pass arguments
and environment variables using the "standard" established by Mark Williams
Company's Micro Shell (msh) and compiler libraries.   MT C-Shell does *not*
convert the arguments to uppercase.   Some C-runtime utilities (namely the
one Atari shipped to developers) converts arguments to *lower* case before
placing them in argv[].

The MWC argument/environment passing method is documented in their manual.
If anyone is interested in the format and cannot obtain by other means,
contact me and I will send you some info.
-- 
David Beckemeyer			|
Beckemeyer Development Tools		| "Reckon the Ball's plumb open now,
478 Santa Clara Ave, Oakland, CA 94610	| and it's `swing partner'!"
UUCP: {rutgers,sun}!hoptoad!bdt!david 	|