# # rvalue, lvalue
APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

rvalue, lvalue

I've removed advertising from most of this site and will eventually clean up the few pages where it remains.

While not terribly expensive to maintain, this does cost me something. If I don't get enough donations to cover that expense, I will be shutting the site down in early 2020.

If you found something useful today, please consider a small donation.



Some material is very old and may be incorrect today

© June 2005 Tony Lawrence

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 the 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.


If you found something useful today, please consider a small donation.



Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> rvalue, lvalue

1 comment


Inexpensive and informative Apple related e-books:

iOS 10: A Take Control Crash Course

Sierra: A Take Control Crash Course

Digital Sharing Crash Course

Take Control of IOS 11

Take Control of iCloud





More Articles by © Tony Lawrence







Sun Jun 5 05:40:13 2005: 613   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<

------------------------


Printer Friendly Version

Have you tried Searching this site?

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.

Contact us


Printer Friendly Version





All of science is nothing more than the refinement of everyday thinking. (Albert Einstein)




Linux posts

Troubleshooting posts


This post tagged:

Programming



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode