From: John Richard Moser <nigelenki@comcast.net>
To: Micha Feigin <michf@post.tau.ac.il>
Cc: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: Re: "static const" attribute in C++ (How to ?)
Date: Wed, 30 Jun 2004 16:39:47 -0400 [thread overview]
Message-ID: <40E32513.1090502@comcast.net> (raw)
In-Reply-To: <20040630013316.GF9412@luna.mooo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Micha Feigin wrote:
| On Tue, Jun 29, 2004 at 06:43:23PM +0100, Glynn Clements wrote:
|
|>It doesn't matter. A #include directive simply inserts the contents of
|>the header file directly into the source code which is fed to the
|>compiler. The compiler doesn't care which file a given piece of code
|>comes from.
|>
|
| It is a problem since a header can be included more then once, and
Umm.
#import "foo.h"
This includes only one time. I'd only use this with Objective-C though.
For C, and in general, you should use:
#ifndef __FOO_H__
#define __FOO_H__
....
#endif /*__FOO_H__*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA4yUShDd4aOud5P8RAkoxAJ9mYFKq+MYzPsX+LGbg/iTDA+UFqQCfYnMv
2Tn7bkzzlPu66jmrOamHJW8=
=nfHE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-30 20:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 22:46 "static const" attribute in C++ (How to ?) Luciano Moreira - igLnx
2004-06-28 23:52 ` Glynn Clements
2004-06-29 14:30 ` Luciano Moreira - igLnx
2004-06-29 17:26 ` Henry Margies
2004-06-29 19:10 ` Luciano Moreira - igLnx
2004-07-02 7:47 ` wwp
[not found] ` <40E56EFF.1030901@ig.com.br>
2004-07-02 14:30 ` Luciano Moreira - igLnx
2004-06-29 17:39 ` Glynn Clements
2004-06-29 14:32 ` Micha Feigin
2004-06-29 17:43 ` Glynn Clements
2004-06-30 1:33 ` Micha Feigin
2004-06-30 2:01 ` Glynn Clements
2004-06-30 23:42 ` Daniel Brockman
2004-07-01 22:33 ` Glynn Clements
2004-06-30 20:39 ` John Richard Moser [this message]
2004-06-30 22:31 ` Glynn Clements
2004-07-01 3:22 ` Micha Feigin
2004-07-01 4:27 ` Glynn Clements
2004-07-01 7:12 ` John Richard Moser
2004-06-29 19:08 ` Luciano Moreira - igLnx
-- strict thread matches above, loose matches on Subject: below --
2004-07-02 10:20 Dinesh Ahuja
2004-07-02 14:29 ` Luciano Moreira - igLnx
2004-07-02 22:32 ` Glynn Clements
2004-07-03 0:12 ` Luciano Moreira - igLnx
2004-07-05 5:35 ` Dinesh Ahuja
2004-06-28 21:42 Luciano Moreira - igLnx
2004-06-28 21:52 ` Glynn Clements
2004-06-29 1:10 ` Micha Feigin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40E32513.1090502@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-c-programming@vger.kernel.org \
--cc=michf@post.tau.ac.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.