Book name for multifileing in c++

[Muzammil]

Hi, i want to learn about multi-fileing in c++ . Can anyone tell me a
good reference book?.
I dont have good idea over multifileing (header files, and
resource file what they do and how it generate object of class in
it).

--
Muzammil Peer

[Mike Wahler]

"Muzammil" <mu*************@gmail.comwrote in message
news:66**********************************@x41g2000 hsb.googlegroups.com...

Hi, i want to learn about multi-fileing in c++ . Can anyone tell me a
good reference book?.

I think you're talking about the fact that
a C++ program can be divided into multiple
source files. Headers (both standard and user
defined) have their text pasted into a source
file wherever an #include directive appears in
the source file. This combination is known as
a 'translation unit'. Translation units are
separately compiled, and then linked together
along with used items from the standard library
to create the final executable.

Most implementations can do the compile and link
without user intervention, or allow these steps
to be performed 'manually'.

I dont have good idea over multifileing (header files, and
resource file what they do and how it generate object of class in
it).

C++ does not have a concept of 'resource files'; you'll
need to consult support resources for your platform
(Windows?) for that.

Your compiler's documentation
(and/or its vendor's support resources) would be the best
place to learn how to build a multiple-source C++ program.

-Mike

[saya-jin]

On Aug 21, 8:48*am, Muzammil <[e-mail]:

Hi, i want to learn about multi-fileing in c++ . Can anyone tell me a
good reference book?.
I dont *have good *idea over *multifileing (header *files, and
resource file what *they do and how *it generate *object of *class in
it).

--
Muzammil Peer

I think there isn't a book about these things because it completely
ups to coding style that you are using. As Mike said C/C++ have the
opportunity to include files to each 'translation unit' and you can
use this feature whatever you would like to. Basically an include file
is for declare the symbols that you are using not just in your module
but in the other ones to. For example if you have a class it's
declaration could be in a separated header file to reference to this
class from an other module. If you would like see some examples or
specification about this matter you need to have a look to some
detailed code style reference like:
- http://google-styleguide.googlecode....k/cppguide.xml
- http://gcc.gnu.org/onlinedocs/libstd...k01apas03.html
etc.