I've also seen this error/warning happen when you mess up your pointer
assignments and try to assign a value to a pointer and visa-versa.
-----Original Message-----
From: Joe Wronski <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, November 17, 1999 6:19 AM
Subject: RE: simple programming question
>An lvalue is just what it says it is. The left side of an assignment
>statement. Sometimes it happens when the variable has the same name as a
>defined macro. This happens quite a bit with simple, case-insensitive
>compilers, or when you have long variable names that are internally
>truncated making it non-ambiguous.
>
>Joe W.
>
>> -----Original Message-----
>> From: Palm Dev Forum [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, November 16, 1999 6:08 PM
>> To: [EMAIL PROTECTED]
>> Subject: simple programming question
>>
>>
>> Sometimes I try to compile and get an error where the compiler
>> tells me that
>> my variable is not a "lvalue". Most of the time I just mess
>> around with it
>> until it goes away but I think I would be better off if I fully
understood
>> what was going on. Could someone please help me out?
>>
>> Thanks.
>>
>>
>>
>
>
