🚀 go-pugleaf

In article <MTM4.1214.010BD7A3@rsvl.unisys.com>, MTM4@rsvl.unisys.com (Mike McCormick) writes:
|> However, there is an alternative to changing the standard which I have not 
|> seen mentioned here yet.  That is, public const pointers:
|> 
|> class Thing :
|> 	pReadOnly(&readOnly)
        ^^^^^^^^^^^^^^^^^^^^ - you mixed class and ctor.
|> {
|> private:
|> 	int readOnly;
|> public:
|> 	const int* const pReadOnly;
|> };

Unfortunatly, now every instance gets an additional pointer.
If one could declare, that every ctor of Thing initializes
pReadOnly the same way so that for every instance pReadOnly
points to the same attribute, then pReadOnly could be optimized
away (like global const).

This is an example where it would be usefull to be able to initialize
not only static but also nonstatic datamembers inside the class defn.

  class Thing {
  private:
	int readOnly;
  public:
	const int* const pReadOnly = &readOnly; // ILLEGAL
  };

[ Regarding how hard it was to introduce this for static members
it seems unlikely to be allowed for nonstatic members. ]


Ulf Schuenemann

--------------------------------------------------------------------
  ,_.   Ulf Schünemann
 #,  \  Fakultät für Informatik, Technische Universität München, Germany.
  |   > email: schuenem@informatik.tu-muenchen.de
  v=-<  WWW:   http://hphalle2.informatik.tu-muenchen.de/~schuenem/

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]