How does printf() works

[Sanchit]

I want to know how does printf (stdio library function) works? Does
this depand on complier (I am using gcc on Linix)

Does it uses some buffer in which it stores all what needed to be
printed and in end of program it prints that or something else.

[Tomasz bla Fortuna]

Dnia Sat, 22 Mar 2008 04:35:24 -0700 (PDT)
Sanchit <sa************ @gmail.comnapis a³(a):

I want to know how does printf (stdio library function) works? Does
this depand on complier (I am using gcc on Linix)

Uhm. It depends on implementation (so on the library not the compiler
itself).

Does it uses some buffer in which it stores all what needed to be
printed and in end of program it prints that or something else.

You'll best just grab the glibc source and find this implementation.
--
Tomasz bla Fortuna
jid: bla(at)af.gliwi ce.pl
pgp: 0x90746E79 @ pgp.mit.edu
www: http://bla.thera.be

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFH5PKhT6w vGJB0bnkRAucXAJ 9MXo8HWUUBIAenK RAWW0FKCHrW5ACg nzXR
2PyUKHQKgpmKh83 NlFQjHKM=
=2kU+
-----END PGP SIGNATURE-----

[Harald van =?UTF-8?b?RMSzaw==?=]

On Sat, 22 Mar 2008 12:50:53 +0100, Tomasz bla Fortuna wrote:

Dnia Sat, 22 Mar 2008 04:35:24 -0700 (PDT) Sanchit
<sa************ @gmail.comnapis ał(a):

>I want to know how does printf (stdio library function) works? Does
this depand on complier (I am using gcc on Linix)

Uhm. It depends on implementation (so on the library not the compiler
itself).

It depends on both the library and the compiler. For example, the
compiler may choose to transform
(void) printf("Hello, world!\n");
into
(void) puts("Hello, world!");
which behaves the same, but works differently.

[Sanchit]

On Mar 22, 4:50 pm, Tomasz bla Fortuna <[e-mail] rote:

Dnia Sat, 22 Mar 2008 04:35:24 -0700 (PDT)
Sanchit <sanchitgupt... @gmail.comnapis a³(a):

I want to know how does printf (stdio library function) works? Does
this depand on complier (I am using gcc on Linix)

Uhm. It depends on implementation (so on the library not the compiler
itself).

Does it uses some buffer in which it stores all what needed to be
printed and in end of program it prints that or something else.

You'll best just grab the glibc source and find this implementation.

--
Tomasz bla Fortuna
jid: bla(at)af.gliwi ce.pl
pgp: 0x90746E79 @ pgp.mit.edu
www:http://bla.thera.be

signature.asc
1KDownload

I have done that already.. but there is not much description

[Richard Tobin]

In article <cb************ *************** *******@e10g200 0prf.googlegrou ps.com>,
Sanchit <sa************ @gmail.comwrote :

>I want to know how does printf (stdio library function) works? Does
this depand on complier (I am using gcc on Linix)

Mostly it depends on the C library implementation. The compiler
itself may know about printf() (for example, so that it can warn about
mismatches between the format and the arguments) but it doesn't have
to.

>Does it uses some buffer in which it stores all what needed to be
printed and in end of program it prints that or something else.

printf() typically works by going through the format string, outputting
the plain characters. When it comes to a % it gets the next argument
using va_arg with a type depending on the format, and then converts it
to characters and outputs it.

The output is done by calling putc() on each character - or by some
equivalent method - and that will do the usual buffering of
characters. Usually for output to a terminal it will save up the
characters until it's got a whole line, and for output to a file it
will save them up until it's got a reasonable size block. If there
are still any characters waiting in the buffer when the program ends,
they are output then. Outputting each character individually would be
slower. You can use the function setvbuf() to control the buffering.

-- Richard

--
:wq

[Sanchit]

On Mar 22, 5:21 pm, ri*****@cogsci. ed.ac.uk (Richard Tobin) wrote:

In article <cb************ *************** *******@e10g200 0prf.googlegrou ps.com>,

Sanchit <sa************ @gmail.comwrote :

I want to know how does printf (stdio library function) works? Does
this depand on complier (I am using gcc on Linix)

Mostly it depends on the C library implementation. The compiler
itself may know about printf() (for example, so that it can warn about
mismatches between the format and the arguments) but it doesn't have
to.

Does it uses some buffer in which it stores all what needed to be
printed and in end of program it prints that or something else.

printf() typically works by going through the format string, outputting
the plain characters. When it comes to a % it gets the next argument
using va_arg with a type depending on the format, and then converts it
to characters and outputs it.

The output is done by calling putc() on each character - or by some
equivalent method - and that will do the usual buffering of
characters. Usually for output to a terminal it will save up the
characters until it's got a whole line, and for output to a file it
will save them up until it's got a reasonable size block. If there
are still any characters waiting in the buffer when the program ends,
they are output then. Outputting each character individually would be
slower. You can use the function setvbuf() to control the buffering.

-- Richard

--
:wq

can u please tell me a source where i can read this behaviour

[J. J. Farrell]

Richard Heathfield wrote:

Johannes Bauer said:

>Are there some weird compilers out there which
omit a warning if the return value is discarded?

No doubt - but then who's to say there isn't some weird compiler out there
that warns about useless casts?

Both have existed; I once had the joy of writing a program which was
supposed to compile without warnings on one of each ...

[CBFalconer]

Sanchit wrote:

>

.... snip ...

>
can u please tell me a source where i can read this behaviour

u hasn't posted here for some years.

--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home .att.net>
Try the download section.

--
Posted via a free Usenet account from http://www.teranews.com

[CBFalconer]

Johannes Bauer wrote:

>

.... snip ...

>
But the transformation from printf to puts - although I know that
gcc does it - is it legal at all, according to the standard? I
could preload some library which overrides printf() - it would
never get called if the compiler subsituted the call by a puts().

No you can't. So doing involved undefined behaviour. See the
standard. The names of standard functions are reserved.

--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home .att.net>
Try the download section.

--
Posted via a free Usenet account from http://www.teranews.com

[Amandil]

On Mar 22, 6:37 pm, CBFalconer <cbfalco...@yah oo.comwrote:

Sanchit wrote:

... snip ...

can u please tell me a source where i can read this behaviour

u hasn't posted here for some years.

[mail]: Chuck F (cbfalconer at maineline dot net)

That piece of nastiness was totally uncalled for, as a polite response
would have the same effect. Your English isn't that much better ("So
doing...)... I believe several of the regulars have plonk()'ed you for
your mostly useless noise. I only wish I knew how to do that with
google...

On a slightly (but only a very slightly) more serious note, printf is
probably implemented as a wrapper:
int printf(char *format, ...)
{
int i;
va_list v;
va_start(v, format);
i = vfprintf(stdin, format, v);
va_end(v);
return v;
}

As for a 'real' implementation - one that actually does the work of
stepping through the format string - K&R2 has a basic version that
only recognizes %i and %s in one of the chapters. The method was
mentioned earlier, no need to repeat it.

On another note, printf() and puts() cannot be exchanged: the former
returns the number of characters printed, the latter returns "a
nonnegative value" (7.19.7.10.3).

Regarding casting the returns from printf() to void: Some of my C
texts mentioned them as needed by some C error-catchers, such as lint.
I personally find they get in the way of reading code.

While signing off, I'd like to reference something I posted in my very
first post on clc: Easter this year is not two and a half weeks later
than last year. Next year, however, it occurs on April 12, which is
almost three weeks later than this year. This is caused by the
addition of a whole month in the lunar calendar. The exact placement
of this month is obviously not the same by all, as I conclude with...

Happy Purim.
-- Marty (not such a newbie anymore, and fully capable of starting a
flame war...)