Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Not really an lvalue" warnings



On 4/6/07, Marshall Clow <email@hidden> wrote:
At 2:48 PM -0700 4/6/07, Mark Wagner wrote:
>The following code produces a warning from GCC about "target of
>assignment not really an lvalue; this will be a hard error in the
>future".  What's going wrong, and how do I fix it?
>
>       char *typeOfQ = NULL;
>       static_cast<const char *>(typeOfQ) =
>handle.FirstChildElement("fieldlabel").Element()->NextSiblingElement("fieldentry")->GetText();

GCC is telling you that there is a problem in your code (hence the
warning), and telling you that future versions of the compiler will
flag this as an error rather than a warning.

This expression:
        static_cast<const char *>(typeOfQ)
is not a variable, it is a expression.

Think of the difference between 'x' and '3' - one can be assigned to,
the other cannot )
Googling for "rvalue" and "lvalue" will give more general information.

I know the difference between an lvalue and an rvalue. My understanding is that "static_cast<const char *>(typeOfQ)" is functionally and semantically equivalent to "(const char *)typeOfQ" with the addition of compile-time checking to make sure the conversion is defined.

--
Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden
References: 
 >"Not really an lvalue" warnings (From: "Mark Wagner" <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.