On 10/23/07, Andrew Lentvorski <[EMAIL PROTECTED]> wrote:
> Carl Lowenstein wrote:
> > On 10/23/07, Andrew Lentvorski <[EMAIL PROTECTED]> wrote:
> >>
> >> What does:
> >> #include <stdio.h>
> >>
> >> mean? Which stdio.h? From where? In what order?
> >
> > Is this a rhetorical question?
>
> Yes, it is rhetorical.
>
> The point is that a zillion things *outside of your control* can affect
> the answer to that question.
>
> And, I'm pretty sure your answer isn't valid if things have been built
> for newlib (a standard library for embedded systems).
>
I thought that if you were building software for a non-standard system
that you should not blindly #include <stdio.h> but would explicitly
include the headers appropriate for that system.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
