[uClibc]<stdio.h> conflicts with <varargs.h>
Erik Andersen
andersen at codepoet.org
Thu Jan 17 17:45:07 UTC 2002
On Fri Jan 18, 2002 at 02:35:20AM +0900, Miles Bader wrote:
> Erik Andersen <andersen at codepoet.org> writes:
> > Why not just use stdarg.h?
>
> Because it's nice be able to compile programs without hacking them all
> to bits, when possible. Often there's no choice -- a program simply
> does something stupid, and won't work without changes -- but <stdarg.h>
> and <varargs.h> have coexisted for a long time, and it's not really a
> problem to support them both.
>
> [The program in question, incidentally, was telnet, as distributed in
> in uClinux-dist-xxx]
K, I'll take a look. Generally speaking though, I consider
direct use if varargs.h by applications a bug, since stdarg.h is
defined by things like POSIX. The Single Unix Spec Ver.2 does
support it, but labels it as LEGACY and states "Use of
<varargs.h> is not recommended.". So I'll probably fix it, but I
really don't plan to expend too much effort supporting obsolete
interfaces. It is really better to fixup applications in this
case.
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
More information about the uClibc
mailing list