From: Nick Garnett <nickg@ecoscentric.com>
To: <sidharth@clarinox.com>
Cc: <ecos-discuss@sources.redhat.com>, <gokhan@clarinox.com>
Subject: Re: [ECOS] Problem with printf
Date: Tue, 18 May 2004 11:38:00 -0000 [thread overview]
Message-ID: <m37jva5csd.fsf@miso.calivar.com> (raw)
In-Reply-To: <200405180741.i4I7fDM00387@mail002.syd.optusnet.com.au>
"Sidharth Jandhyala" <sidharth@clarinox.com> writes:
> Why has eCos been implemented such that the '\n' must be included at the end
> of the printf statement. Is there a way to avoid this characteristic. Is
> there a way to flush the print buffers other than looking for the '\n'.
This is standard C library behaviour. The library buffers all output
characters internally until either the buffer is full or, for line
buffered streams, a newline is output. If you want to cause buffered
data to be output before either of those conditions occurs, use
fflush(stdout).
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-05-18 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 9:02 Sidharth Jandhyala
2004-05-18 11:38 ` Nick Garnett [this message]
2004-05-19 8:07 ` Sidharth Jandhyala
2004-05-19 9:39 ` sandeep
2004-05-31 10:41 ` Gokhan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37jva5csd.fsf@miso.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gokhan@clarinox.com \
--cc=sidharth@clarinox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).