From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Alternative to fcvt for older DJGPP? Date: 6 Aug 2003 09:48:21 GMT Organization: Aachen University of Technology (RWTH) Lines: 15 Message-ID: References: <76uzeozd7s3g.1sgoajp58hmqa$.dlg AT 40tude DOT net> <1sb2cgsjrn9c1.1qat04crl2pqh$.dlg AT 40tude DOT net> <15oavr9z6uf0m$.1l1oz07obzrud DOT dlg AT 40tude DOT net> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1060163301 19947 137.226.32.75 (6 Aug 2003 09:48:21 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 6 Aug 2003 09:48:21 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Quasar wrote: > Aside from the use of fcvt in one place, the rest of the code is pure > ANSI C. Pardong the French, but that's quite a piece of nonsense. It makes about as much sense as "Aside from the cockroach living over there by the fridge, the rest of our kitchen is perfectly clean". fcvt() is entirely unportable, and thus an implementation of snprintf using it cannot ever be called portable, either. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.