From:	Martin Ambuhl <mambuhl AT earthlink DOT net>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language:	en-us, en, de, fr, ru, el, zh
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Alternative to fcvt for older DJGPP?
References:	<76uzeozd7s3g.1sgoajp58hmqa$.dlg AT 40tude DOT net>
In-Reply-To:	<76uzeozd7s3g.1sgoajp58hmqa$.dlg@40tude.net>
Lines:	17
Message-ID:	<2_pXa.4525$kP6.1393@newsread2.news.atl.earthlink.net>
Date:	Mon, 04 Aug 2003 09:48:46 GMT
NNTP-Posting-Host:	65.145.36.123
X-Complaints-To:	abuse AT earthlink DOT net
X-Trace:	newsread2.news.atl.earthlink.net 1059990526 65.145.36.123 (Mon, 04 Aug 2003 05:48:46 EDT)
NNTP-Posting-Date:	Mon, 04 Aug 2003 05:48:46 EDT
Organization:	EarthLink Inc. -- http://www.EarthLink.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Quasar wrote:

> I have a program that needs to compile with an older version of
> DJGPP which does not appear to have fcvt in its libc. Are there
> any quick alternatives to this function? (This part of the code
> was SUPPOSEDLY universally portable, but I see that fcvt is not
> standard at all, so I'm in a fix).

Just use sprintf(); there is no function called "fcvt" in the standard C 
libraries, while sprintf is there.  Even those of us who are die-hard 
gcc fans know to avoid non-portable constructs when there is an 
acceptable solution in the standard libraries.


-- 
Martin Ambuhl

- Raw text -