This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: #pragma interface and #pragma implementation
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 03 June 2004 06:01, Gabriel Dos Reis wrote:
> "Steven T. Hatton" <hattons@globalsymmetry.com> writes:
>
> Practically, it means anything that can be #included -- so, while it
> is common to have files with suffixes .h, .H ... as header files, you
> can also have .C files as "header files". Don't read too much into
> "header" in "header files". In particular, an "implementation file"
> could also be (its own) header file.
I don't want to clutter this list with a bunch of newbie noise, but since you
came back so fast, and this is probably an easy question, I'll ask.
The part that I don't understand is what does GCC think a source file is?
That is, if there is a 1-1 correspondence between a source file and a
translation unit, and anything that looks like C++ can be considered either
source or header, there has to be some mechanism. I'm guessing "source file"
means whatever follows the `g++ [options]' on the commandline.
> Let's those pragmas die.
I'm still wondering who wrote that part of the documentation. I'm interested
in the idea, even if it was an incorrect explanation of what the #pragmas do.
Also, I don't have enough background to form an opinion as to the usefullness
of the #pragmas, but I do have enough experience to know that if they aren't
removed, the documentation should be corrected.
- --
Regards,
Steven
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFAvvsuwX61+IL0QsMRAnJTAKCp32Dub7rxjTNgCmyxQIL89iUclACfe8St
ewcEnX9e6+DfUndK3N/zIA4=
=Hj00
-----END PGP SIGNATURE-----