This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Problem with printf


Fflush seems like not working for EB40A ( unless we are making a silly
mistake ). Is there any setting that could have missed during the
configuration?

Thanks in advance, 

Gokhan Tanyeri
www.clarinox.com

-----Original Message-----
From: nickg@miso.calivar.com [mailto:nickg@miso.calivar.com] On Behalf
Of Nick Garnett
Sent: Tuesday, May 18, 2004 7:02 PM
To: sidharth@clarinox.com
Cc: ecos-discuss@sources.redhat.com; gokhan@clarinox.com
Subject: Re: [ECOS] Problem with printf


"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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]