Re: Can copy assignment operator be const?
On 2 Dec 2006 03:08:03 -0500, James Kanze wrote:
[...]
My question is: would you consider my implementation of
dynamic_bitset::reference defective in this regard?
<http://preview.tinyurl.com/uew6m>
I'd have to study it. Off hand, it looks like it should work.
Well, it works :-)
That's a broad statement. Define "works".
Define "should work" :-P
Can I write something like:
sometype* p = &a[i] ;
?
class reference {
...
void operator&(); // left undefined
...
};
[...]
The idea to return a bool from
bool operator=(bool x) const { do_assign(x); return x; }
is particularly nice.
Maybe. Is it intended that users declare things like
dynamic_bitset::reference? Do you want to support something
like:
dynamic_bitset::reference
someFunction()
{
// ...
return a[ i ] = someValue ;
}
(I could do this with a vector<int> and vector<int>::reference,
for example.)
You seem to be jumping the gun. I didn't say I'm going to use it, just
that the idea is nice. It isn't universally appliable. In my case I
have to return a (const) refererence &; it was my intent to support
the above (with "typename" and a couple of angle brackets), and it
worked last time I touched the code, but I don't think the issue has
received much scrutiny.
--
Gennaro Prota. C++ developer. For hire.
(to mail me, remove any 'u' from the address)
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]