Xref: utzoo comp.sources.wanted:17319 alt.sources.wanted:1398 comp.lang.c:40600 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!agate!dog.ee.lbl.gov!elf.ee.lbl.gov!torek From: torek@elf.ee.lbl.gov (Chris Torek) Newsgroups: comp.sources.wanted,alt.sources.wanted,comp.lang.c Subject: Re: Portable mini-vfprintf? Message-ID: <14814@dog.ee.lbl.gov> Date: 30 Jun 91 02:03:59 GMT Article-I.D.: dog.14814 References: <25767@well.sf.ca.us> <25777@well.sf.ca.us> Reply-To: torek@elf.ee.lbl.gov (Chris Torek) Organization: Lawrence Berkeley Laboratory, Berkeley Lines: 16 X-Local-Date: Sat, 29 Jun 91 19:03:59 PDT In article <25777@well.sf.ca.us> Jef Poskanzer writes: >To support floating-point output in the mini-vfprintf, I added a call >to gcvt. How portable is this? Not. >Chris Torek suggested I just call _doprnt instead of vfprintf - same >args, different order. How portable is this? Also not. Let me clarify a bit: I suggested using vfprintf where it exists, and where it does not, falling back on _doprnt. Most `supported' systems have at least the ANSI C libraries (if not the syntaxes), and most `unsupported' C systems seem to be aging Unix systems. -- In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 415 486 5427) Berkeley, CA Domain: torek@ee.lbl.gov