Re: printf behaviour with illegal or malformed format string
- From: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx>
- Date: Tue, 13 Dec 2005 14:00:51 +0100
In message <20051213230723.T3248@xxxxxxxxxxxxxxx>, Bruce Evans writes:
>Now I think they should be very rarely needed and more rarely used.
>Using them mainly gives unportable code that breaks especially badly
>on systems which don't support extensions.
Portability is good, but it shouldn't get in the way of improving
our programs.
>I think these belong in specialized applications or libraries. %T is
>already handled better by strftime/gmtime/localtime.
There's no handling for fractional seconds there.
>I mean aborting instead of returning NULL for failing malloc()s breaks
>defined behaviour.
Right, that's deliberate.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
- References:
- Re: printf behaviour with illegal or malformed format string
- From: Bruce Evans
- Re: printf behaviour with illegal or malformed format string
- Prev by Date: Re: printf behaviour with illegal or malformed format string
- Next by Date: Re: printf behaviour with illegal or malformed format string
- Previous by thread: Re: printf behaviour with illegal or malformed format string
- Next by thread: Re: printf behaviour with illegal or malformed format string
- Index(es):