Re: returning lvalue in C vs C++
- From: Ben C <spamspam@xxxxxxxxx>
- Date: 29 Mar 2006 22:55:47 GMT
On 2006-03-29, Phlip <phlip2005@xxxxxxxxx> wrote:
Ben C wrote:
f().x = 200; /* "invalid lvalue" in C, but not in C++ apparently */
Consider the general scheme of C++, and specifically its overloaded
operators.
x.operator=() (figuratively) could have a side-effect that your code depends
on. So regardless where 'thing' appears, thing.x is accessible as an
lvalue.
It would be thing.operator=() but I see the point.
I did think of that, but I'm not sure it's the answer.
.
- Follow-Ups:
- Re: returning lvalue in C vs C++
- From: Ben C
- Re: returning lvalue in C vs C++
- References:
- returning lvalue in C vs C++
- From: Ben C
- Re: returning lvalue in C vs C++
- From: Phlip
- returning lvalue in C vs C++
- Prev by Date: Re: returning lvalue in C vs C++
- Next by Date: Re: returning lvalue in C vs C++
- Previous by thread: Re: returning lvalue in C vs C++
- Next by thread: Re: returning lvalue in C vs C++
- Index(es):