• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 1183 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Transferring Array Data/ Error Message c213

Andre Lubarsky Jr.


In trying to compile the following ( trivial to me) C code with the C51
compiler, I received error c213 "left side of asn-op not an lvalue" -
" the address of a changeable object is required at the right side of the
assignment operator".

Code:
unsigned int A[8];
unsigned int B[8];
unsignned int i;

for (i = 0; i = 7; i++)
A[i] = B[i]; /* error here */

Is it the compiler or the code???

Any help or comments appreciated.

Thanks

Andy

  • 0

    The following code seems to work OK:

    void main (void)
{
unsigned int A[8];
unsigned int B[8];
unsigned int i;

for (i = 0; i < 8; i++)
  {
  A[i] = B[i]; /* error here */
  }
}

    In your code, there are few problem that prevent testing:

    1. unsignned int i: I assume this is really unsigned.

    2. for (i = 0; i = 7; i++): The middle expression of a for statement should be a comparison, not an assignment.

    Keil Support

  • 0 

    unsigned int A[8];
unsigned int B[8];
unsignned int i;

for (i = 0; i = 7; i++)
A[i] = B[i]; /* error here */

    There is a typo in your 3rd line: 
    unsignned int i
    Did the compiler report an error on this line?

    It seems to be a "feature" of the Keil compiler that it will report this error (C213) on every line containing an array reference after any other error has been reported on a previous line.
    Maybe Keil support could comment on this?

    In any compiled language, you should always fix the first reported error first; chances are this will also fix many of the following "errors," which were just due to the compiler getting out-of-step with your intentions.

    BTW: Check out the "Tips for Posting Messages" link in the sidebar to see how to do the code quotes, italics, bold, etc.