🚀 go-pugleaf

In article <Pine.A32.3.91.960325093715.29874A-100000@zorglub.cae.ca>
dak <pierreba@poster.cae.ca> writes:

|> I've just encountered a problem in one of our template design and wondered
|> what could be done about it. It concerns const reference return value from
|> a templated member function, for example:

|> template <class T> class SmartPtr
|> {
|> 	// ... whatever:
|> public:
|> 	const T & Dereference ();
|> };

|> The problem arise when T is instantiated with a Container of constants:

|> SmartPtr<const int> a;

|> Here we have a double const which is not supported by the compiler, nor the
|> standard, I believe.  Is there a fix or should we abandon all hope of using
|> const returns in templates ?

The draft standard forbids two explicit const's.  If the duplicate
Const result from typedef's, etc., it's OK.  (I don't know if the
actual words mention template instantiation types, but if they don't
I'm sure that it is an editorial oversight, and not the intent.)

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