linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 29 Jun 2004 17:32:38 +0300	[thread overview]
Message-ID: <20040629143238.GD6335@luna.mooo.com> (raw)
In-Reply-To: <16608.44836.384260.844173@cerise.nosuchdomain.co.uk>

On Tue, Jun 29, 2004 at 12:52:04AM +0100, Glynn Clements wrote:
> 
> Luciano Moreira - igLnx wrote:
> 
> > Is very commom in Java, the declaration of "static const" attributes 
> > into class escope. Is possible to do anything similar in C++ ?
> > Using another techniques ?
> > 
> > All we need is to have a public static symbol into a class escope that 
> > can be used to declare a array, intead of using a lot of global symbols.
> 
> It appears that you are allowed to initialise constant static members
> within the declaration, so you can do this:
> 
> 	class Foo
> 	{
> 	public:
> 		static const int DEFSIZE = 100;
> 	};
> 	
> 	class Bar
> 	{
> 	public:
> 		char myArray[Foo::DEFSIZE];
> 	};
> 
> 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?

> 
> -- 
> 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.
> 

  parent reply	other threads:[~2004-06-29 14:32 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 [this message]
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
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=20040629143238.GD6335@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).