linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Moreira - igLnx <lucianolnx@ig.com.br>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: "static const" attribute in C++ (How to ?)
Date: Fri, 02 Jul 2004 11:29:16 -0300	[thread overview]
Message-ID: <40E5713C.3060009@ig.com.br> (raw)
In-Reply-To: <20040702102014.58508.qmail@web8310.mail.in.yahoo.com>

Yes ! It was my solution.

Luciano

Dinesh Ahuja wrote:

>Hi Henry,
>
>There is a concept of constant folding in C++.
>Whenever you declare any data member of class as a
>constant, the compiler should allocate the memory for
>it in the object layout and compiler should know the
>size of the variable in advance. Suppose, if I have a
>class like below :
>class MyClass {
>   const int size;
>   int arrSize[size];
>};
>This will not compile because compiler can not do the
>constant folding in above case as memory needs to be
>allocated for the constant data member size.
>
>The above problem can be resolved by using enums.
>class MyClass {
>   enum {size = 100};
>   int arrSize[size];
>};
>
>This will work as enum doesn't have any linkage and
>hence no memory is allocated for them. Even use of
>extern keyword prevents constant folding for a
>constant variable.
>
>I hope the above thing may have helped you.
>
>Thanks & Regards
>Dinesh-Ahuja
>
>  
>
>>>Henry Margies wrote:
>>>Just put the definition in the cpp file.
>>>Header File:
>>>class Foo
>>>{
>>>	public:
>>>		static const int DEFSIZE;
>>>};
>>>
>>>in CPP-File:
>>>
>>>const int Foo::DEFSIZE=100
>>>
>>>Why does this not work for you?
>>>
>>>Henry
>>>      
>>>
>
>
>
>________________________________________________________________________
>Yahoo! India Careers: Over 50,000 jobs online
>Go to: http://yahoo.naukri.com/
>
>
>  
>

  reply	other threads:[~2004-07-02 14:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 10:20 "static const" attribute in C++ (How to ?) Dinesh Ahuja
2004-07-02 14:29 ` Luciano Moreira - igLnx [this message]
2004-07-02 22:32 ` Glynn Clements
2004-07-03  0:12   ` Luciano Moreira - igLnx
2004-07-05  5:35     ` Dinesh Ahuja
  -- strict thread matches above, loose matches on Subject: below --
2004-06-28 22:46 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
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
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=40E5713C.3060009@ig.com.br \
    --to=lucianolnx@ig.com.br \
    --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).