🚀 go-pugleaf

In article <MTM4.1250.01029391@rsvl.unisys.com> MTM4@rsvl.unisys.com (Mike McCormick) writes:

>>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
>>  };
> 
> Just supposing this *were* legal syntax, how is it an improvement over the 
> constructor initializer syntax?

If it were legal, pReadOnly need not take any space in the class becuase
the compiler would always know where it pointed.  Just like `const int
&const pReadOnly = &readOnly;' might do if legal.

With constructor initializer syntax, the compiler can only know where
pReadOnly points if the constructor is inlined.
-- 
Regards,

Hallvard

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