This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: asprintf
- To: "Jerome G. Benoit" <jgmbenoit at wanadoo dot fr>
- Subject: Re: asprintf
- From: Tadeusz Liszka <tad at comco dot com>
- Date: Mon, 17 Jul 2000 12:48:00 -0500
- CC: Cygnus list <cygwin at sourceware dot cygnus dot com>
- Organization: Altair Engineering, Inc.
- References: <396F87B7.E04BBF2A@wanadoo.fr>
I think you are going wrong way - if you try to build transportable code, you
should use only routines in common C libs, and asprintf is not, and certainly
_IO_vasprintf is not portable (if it starts with _ it is by definition system
dependent).
If you cant make sprintf to work (!?!) then your option is to write portable
sprintf yourself (or use the one hanging around - download eprintf, or mktclapp,
to get very good replacement for it written by Dr. Hipp)
http://www.hwaci.com/sw/mktclapp/
Jerome G. Benoit wrote:
>
> Bonjour
>
> I have some trouble with `sprintf' (not on Cygnus but elsewhere)
> and I want to write transportable codes:
> I guess that I can use `asprintf' instead (see GNU Lib C doc).
> I did not find `asprintf' in headers distributed with Cygnus
> but I found `int _IO_vasprintf ...' in `libioP.h'.
>
> It is dangerous to use it ?
>
> Thanks in advance,
> Jerome
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Tadeusz
:: The public opinion should be alarmed by its own nonexistence
:: (512)467-0618 ext. 526 :: Stanislaw J. Lec, trans. TJL
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com