From: Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Question of fprintf...
Date: 14 Mar 2000 12:48:10 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 17
Message-ID: <8alcea$e6q$1@nets3.rz.RWTH-Aachen.DE>
References: <38C88020 DOT 19C85510 AT ou DOT edu> <MPG DOT 13335fc6b5b7364898b982 AT news DOT freeserve DOT net> <38C98EE3 DOT DFCCAEF9 AT ou DOT edu>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 953038090 14554 137.226.32.75 (14 Mar 2000 12:48:10 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 14 Mar 2000 12:48:10 GMT
User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586))
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

David Cleaver <davidis AT ou DOT edu> wrote:

>> > cotnum(a, outfile);
>> > fprintf(outfile, "^%d + ", x);

> Because these libraries are used in manipulating really big numbers.
> These are basically objects, and the value "a" in the code snipet is
> a pointer to one of these objects.

That's a rather obvious design bug in that library, then. 'cotnum()'
really should not write out anything besides the number itself, or
offer an option omit that trailing newline.  Better still, it should
work in sprintf() style, presenting its result as a string, which you
can then manipulate in whatever way you have to.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.