Re: GOC a ANSI C superset??

Tony Dean <starnet!apple!lookout.mtt.it.uswc.uswest.com!tdean>

Mail folder: Zoomer-List Mailing List Archives, 1993
Next message: starnet!apple!cadence.com!lrau: "Re: GOC a ANSI C superset?? "
Previous message: Chuck Musciano: "Re: ZPDA FAQ Thingy"

Message-id: <199311161432.AA23083@lookout.mtt.it.uswc.uswest.com>
Date: Tue, 16 Nov 93 07:33:48 -0700
From: Tony Dean <starnet!apple!lookout.mtt.it.uswc.uswest.com!tdean>
To: zoomer-list-1993@grot.starconn.com
Subject: Re:  GOC a ANSI C superset??
Status: OR



> Ran in to an interesting problem this weekend.  I was write a little app
> and needed a function to convert a number to its ascii format so naturally
> the first thing I thought of was ltoa(), however the ANSI (??) C header files
> provided by GeoWorks does not contain a prototype for ltoa() and thus I could
> not link.  

Another interesting tidbit. There is no ltoa() function defined in POSIX
or the C Standard library (ANSI). If you have seen such a function it is 
probably an extension. To perform the task you are interrested in
try the sprintf() function:

	sprintf(some_buffer,"%l",a_long_type);

> I understand that (for various reasons) GeoWorks must provide the C support, 
> however, How do I find a list of C functions not provided?  Trial and error 
> is not a good method.  Is this in one of the manuals??

You might draw comparisons between a good reference on ANSI 'C' and the 
GEOS libraries. Unfortunately many so called ANSI 'C' reference works
for specific DOS based 'C' development environments do not tell you
when you have passed from ANSI into the non-standard extensions provided
by individual development environments. 

Two texts I like regarding Standard 'C' and 'C' portability are
	"The Standard 'C' Library" by Plauer
			and
	"POSIX Programmers Guide" by Donald Lewine


td