This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: Printf doesn't result in a call to write
- From: "Shaun Jackman" <sjackman at gmail dot com>
- To: "Matt Gessner" <mgessner at avidyne dot com>
- Cc: "Dave Korn" <dave dot korn at artimi dot com>, newlib at sourceware dot org
- Date: Mon, 11 Sep 2006 10:42:23 -0600
- Subject: Re: Printf doesn't result in a call to write
- References: <131AF8573CF31945B5B11E4201D3F1E142B9D5@mail3.Avidyne.com>
- Reply-to: "Shaun Jackman" <sjackman at gmail dot com>
On 9/11/06, Matt Gessner <mgessner@avidyne.com> wrote:
I was under the impression that the \n character at the end would bypass
that.
I'll add an fflush to stdout to see if that helps.
Good point, though...
The '\n' character will flush the output buffer if the stdio stream is
line buffered. The stdout stream will be line buffered by default if
isatty(STDOUT_FILENO) returns true, which depends on your target, OS,
libgloss, et cetera.
Cheers,
Shaun