🚀 go-pugleaf

In article <4j49e0$8fo@dub-news-svc-4.compuserve.com> Philippe Verdy
<100105.3120@compuserve.com> writes:

|> Would not it be great if we could simply define such members
|> as "unconst" like in the following example :

|>   class T {
|>   public:
|>     T()                   { ...; _mark = 0; }
|>     virtual ~T();

|>     virtual void show() const;
|>   protected:
|>     void mark() const     { _mark = 1; } // RELAXED HERE
|>     void unmark() const   { _mark = 0; } // RELAXED HERE
|>     bool ismarked() const { return _mark; }
|>   private:
|>     unconst char _mark; // HERE IS WHERE THIS APPLIES
|>   }

You can.  Except that `unconst' is spelled `mutable'.
-- 
James Kanze         Tel.: (+33) 88 14 49 00        email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs-Bourgeois, F-67000 Strasbourg, France
Conseils, études et réalisations en logiciel orienté objet --
                -- A la recherche d'une activité dans une region francophone



[ comp.std.c++ is moderated.  To submit articles: try just posting with      ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu         ]
[ FAQ:      http://reality.sgi.com/employees/austern_mti/std-c++/faq.html    ]
[ Policy:   http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
[ Comments? mailto:std-c++-request@ncar.ucar.edu                             ]