These are terms you'll see in programming, and particularly so in C. I find it's easy to remember these in two ways: An lvalue will be found to the left of an assignment, an rvalue to thye right. You can also think of "l" as the location of the value and "r" as the read-out.
In most contexts, it's pretty obvious which is which, which also means that it's easy for a compiler to know when you screw up. To take a silly example, "b=1" is fine, but "1=b" isn't because "1" obviously is not something that has a location or address: it's probably going to be popped right into a register and used directly. I say "probably" because the compiler is free to assign storage for that if it wanted to, or even to just clear b and increment it if that's a faster way to get "1" assigned. Regardless, "1" is not an lvalue.
But things aren't always that obvious.
main () {
enum color { red, green, blue, indigo };
enum color c;
c = green;
// that's fine
// ..
// lots of other code, and we've forgotten what green really is
green=indigo;
}
That last line will cause an "invalid lvalue in assignment" from the compiler, because "green" is not an lvalue. There are plenty of other ways a beginning programmer can cause similar objections.
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Sun Jun 5 05:40:13 2005: Subject: Bela
Many years ago, I was once involved in debugging a problem on a CP/M (8080) system, in a program written in Microsoft Fortran.
I don't remember many details, but the punchline was: a floating point constant was being passed to a subroutine that modified that argument. After that moment, references to what (in the source) appeared to be the constant "1.0" (or whatever it was) actually returned the modified value.
The moral: sometimes a compilation system unexpectedly _does_ see constants as lvalues. Much to the detriment of your sanity.
>Bela<
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar