Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!osu-cis!n8emr!lwv
From: lwv@n8emr.UUCP (Larry W. Virden)
Newsgroups: comp.std.c
Subject: Thoughts on moving towards ANSI
Message-ID: <795@n8emr.UUCP>
Date: 7 Feb 89 20:16:47 GMT
Reply-To: lwv@n8emr.UUCP (Larry W. Virden)
Distribution: usa
Organization: Ham BBS, 614-457-4227 (1200/2400/19.2 telebit,8N1)
Lines: 23


I have been talking to a software publisher who is working on a new C compiler.
His statement was that he was going to provide as much ANSI as possible, but
that there were some points at which there would be problems, since the existing
environment of C code for this machine (GS/Mac type environment) used a few
special extensions that were incompatible with ANSI.  As an example, he mentioned
that in APW C and I assume MPW C, a printf format of %p was used for 'pascal'
format strings, where the length is specified as a 2 byte (?) value before
the string.  Thus, he wasnt going to be able to support the ANSI %p for pointer
format.

How will other vendors be handling the changing of such things - note that
this isnt a compile time problem but a run time problem.  Will all other
vendors in non-unix environments just force customers to go with the new
standard, become semi-standard, or is there some standard ways someone can
specify whether certain run time interpretations are to be made...


-- 
Larry W. Virden	 674 Falls Place, Reynoldsburg, OH 43068 (614) 864-8817
75046,606 (CIS) ; LVirden (ALPE) ; osu-cis!n8emr!lwv (UUCP) 
osu-cis!n8emr!lwv@TUT.CIS.OHIO-STATE.EDU (INTERNET)
The world's not inherited from our parents, but borrowed from our children.