so Complex this file ! I don't understand why people put " This ... GPL copyright...Without any warranty of merchantability..) every where on 10.000 files of glibc. Each paragraph costs 20 lines of 70 letters . so its 1k. On 10.000files it's 10.000.000 bytes!!!!!!!!!!!!!!!!!!!!!!!!!
I can't print files to read bc of lack of toner due to uneccessary repeatedness

And exactly how am I to assist you? Post addresses of stores for cheap toner refills or edit 10.000 files by removing the (quote) "This ... GPL copyright...Without any warranty of merchantability..)"???

I mean, I would love to but I am slightly busy right now

1 members found this post helpful.

Run the preprocessor like:
The preprocessor will remove comments.

Additionally, you can use awk to remove blank lines.
Moreover, you can use tail to every line after the 20th line.

May be it is wrong place to put my question, But I'm little confuse, & this place I really like to ask..
I study C and I notice I can`t find implementation file for some header files like stdio.h for example. stdio.h contain a lot of i/o functions like printf. Where to find it implementation ?

In source file just add this line:

#include <stdio.h>

That's all.

Okay. I'll make try

Hi,
The implementations are noramally in the .c files. You are unlikely to have these on your system since they are not needed either at run time or when compiling your own code against the libraries (in this case you just need the definitions in the header files and the binary libraries). To get the .c files you should download/install the full source. The easiest way to do this depends on what OS you are running.

Evo2.

The source of glibc is available for downloading, but it is not required for using glibc.

It's also available online and cross-referenced.

Greatest site you posted here... Thanks allot for this site. Really found this helpful to me.

P. J. Plauger's book, The C Standard Library, has source code implementing everything in the standard library. I keep meaning to buy it.

Not an incorrect place, the programming forum, to ask your question. In the future, please start a new thread and refrain from resurrecting 9 year old threads. The interface should've warned you that you were about to re-open a thread which had no activity for greater than 6 months.

Agreed. But, "it's done now."

To answer your direct question, and disregarding the irrelevant corpses: every C-program (like every program in [almost] every other programming language ...) relies upon a set of subroutines which it simply presumes will exist. And of course, they do exist ... but where?

The answer, in the case of programs written in "gcc," is the glibc standard library.

This will usually be a .so file, which means that it is loaded dynamically by Linux anytime any program requiring its services (which, in this case, is "everything") needs to run. That single copy of object-code is then shared by everyone who needs it. It is, as you may well have guessed, a very large and complex library, full of some "seriously voodoo" code.

Strictly speaking, that's not the only way to do it. The necessary subroutines can also be "statically linked" into the executable file, so that no external libraries are then necessary.

The entire process of creating a computer-program in "C" is at least a two-stage process: first, the C source-code is compiled; then, the outputs of the compiler are linked to create a complete executable. (Which may then, as aforementioned, require the services of one-or-more external libraries which will be required to be present every time this program is run.) Most production programs consist of hundreds of ["C" ...] source-files, not all of which must be re-compiled every time: you re-compile only what just got changed, then you link everything (old or new ...) together again. "Rinse and repeat."

stdio.h, among others, provides the compiler with the "header files" needed to know what the runtime routines "look like," so that it can generate appropriate calls to them.