i know i can get everything on google.but my point is i want one or two pdf 
free ebooks just to know it.and a specific just one book.plz help 
me............otherwise i ll lost myself in a sea of C books........



________________________________
From: Tyler Littlefield <[email protected]>
To: [email protected]
Sent: Monday, April 13, 2009 12:01:32 AM
Subject: Re: [c-prog] how to write own header file??





google.com might find you one. amazon.com is worth checking. also bookshare.

Thanks,
Tyler Littlefield
Web: tysdomain.com
email: ty...@tysdomain. com
My programs don't have bugs, they're called randomly added features.

----- Original Message ----- 
From: Snit Roy 
To: c-p...@yahoogroups. com 
Sent: Sunday, April 12, 2009 12:27 PM
Subject: Re: [c-prog] how to write own header file??

plz give an ebook link

____________ _________ _________ __
From: Thomas Hruska <thru...@cubiclesoft .com>
To: c-p...@yahoogroups. com
Sent: Sunday, April 12, 2009 6:55:49 PM
Subject: Re: [c-prog] how to write own header file??

Snit Roy wrote:
> i want a best and summarized solution.plz help 

Short answer: Get a good book.

Longer answer: A header file, by itself, is almost always useless. You 
need code to go with it. When you compile your code, it is typically 
automatically linked against the Standard C/C++ library. This library 
has been precompiled for you and you include things like cstdio, 
iostream, etc. to gain access to the various bits of functionality 
exported by the library. Header files are plain-text files. Go into 
your compiler's directory and look at some of them. You won't see a 
whole lot of code there (if any) - just function declarations, #defines, 
etc. designed for the preprocessor.

-- 
Thomas Hruska
CubicleSoft President
Ph: 517-803-4197

*NEW* MyTaskFocus 1.1
Get on task. Stay on task.

http://www.CubicleSoft.com/MyTaskFocus/

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]





      

[Non-text portions of this message have been removed]

Reply via email to