Message-Id: <200011070016.TAA25138@qnx.com> Subject: Re: snprintf To: djgpp-workers AT delorie DOT com Date: Mon, 6 Nov 2000 19:16:37 -0500 (EST) From: "Alain Magloire" Cc: eliz AT is DOT elta DOT co DOT il In-Reply-To: <3A07124A.E224EB52@bigfoot.com> from "Richard Dawe" at Nov 06, 2000 08:19:22 PM X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > Hello. > > Alain Magloire wrote: > > > > Eli Zaretskii wrote: > > > It's on my todo to get that done, if no one else does it before. Your > > > patches (and the ensuing discussions) are all available via searching > > > the DJGPP mail archives, http://www.delorie.com/djgpp/mail-archives/. > > > > I do not think it is since most of the exchange was not Cc:ed to > > this list. You'll probably find the trivial v/snprintf implementations > > but not the patched to make __putc() or fillbuffer overwrite ^^^ not to > > the buffer when the limit is reach. > > I have the mail exchanges, I think. I can post a summary and put the > patches in my "DJGPP dumpster" > (http://www.phekda.freeserve.co.uk/richdawe/djgpp/ ), if that would help > and Alain & Eli don't object to me quoting the private mail. Not a problem. The patches were trivial, IIRC it changes __putc or putc_raw() for noop when the end of the string buffer(__IOSTR) was reach and when flush() was calling filbuf(), something that should not be for _IOSTR buffers. Sorry I did not have time to finishing it up, hopefully someone with more freetimes could beat some sense into it. -- au revoir, alain ---- Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!