From: Micha Feigin <michf@post.tau.ac.il>
To: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: Re: "static const" attribute in C++ (How to ?)
Date: Wed, 30 Jun 2004 04:33:16 +0300 [thread overview]
Message-ID: <20040630013316.GF9412@luna.mooo.com> (raw)
In-Reply-To: <16609.43579.336662.194984@cerise.nosuchdomain.co.uk>
On Tue, Jun 29, 2004 at 06:43:23PM +0100, Glynn Clements wrote:
>
> Micha Feigin wrote:
>
> > > It appears that you are allowed to initialise constant static members
> > > within the declaration, so you can do this:
>
> > > This compiles with "g++ -ansi -pedantic", so it's probably standard
> > > ISO C++.
> >
> > Does this also work when put in a header or only when put directly in
> > the cpp file?
>
> 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
since the static value is put into the data section of the object, the
linker should give an error if the file was included more the once
since it will have multiple definitions for the same variable and it
wont know how to link the objects (it doesn't care if it the same
values, it does care if the static variable gets its value more then
once).
I had that problem with the arpack++ library which is implemented in
headers only and it sets such a variable and crashes miserably if I
split the code between files.
> --
> Glynn Clements <glynn.clements@virgin.net>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> +++++++++++++++++++++++++++++++++++++++++++
> This Mail Was Scanned By Mail-seCure System
> at the Tel-Aviv University CC.
>
next prev parent reply other threads:[~2004-06-30 1:33 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 [this message]
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
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=20040630013316.GF9412@luna.mooo.com \
--to=michf@post.tau.ac.il \
--cc=linux-c-programming@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).