Re: initializer must be constant error bug?

"Mike H." <mikehg_67@xxxxxxxxx> wrote in message
news:43d61cf5$0$9250$6d36acad@xxxxxxxxxxxxxxxxxxxxxxxx
> Ivan A. Kosarev wrote:
>> "Mike H." <mikehg_67@xxxxxxxxx> wrote in message
>> news:43d5a8db$0$9239$6d36acad@xxxxxxxxxxxxxxxxxxxxxxxx
>>
>>>void foo(int x, int y, int w, int h)
>>>{
>>>RECT rc = { x,y,w,h };
>>>}
>>>
>>>This should work for auto variables, correct?
>>
>> Nope, not in C89. In both C99 and C++ that would be correct.
>>
> I thought Lcc-Win32 was being updated to support C99, maybe not
> implemented yet?, or a switch I'm missing?

Oh, if that wasn't accepted by your LCC-Win32 in C99-compatibility mode,
it's certainly a defect then.

--
Unicals Group -- Embedded C++ for Your IP Cores
http://www.unicals.com


.

Relevant Pages

  • isblank() missing
    ... It is not possible to link the following program with lcc-win32: ... int main(void) ... I think the system is missing the objectcode for isblank. ...
    (comp.compilers.lcc)
  • Re: Is this legal ?
    ... "This is not strictly valid C". ... same level as lcc-win32 but this code below will be accepted by ...
    (comp.lang.c)
  • Re: Is this legal C?
    ... missing semicolon before `mainbody' ... Warning main.c: 4 no type specified. ... Defaulting to int ... That does tend to indicate some failings in lcc-win32. ...
    (comp.lang.c)
  • Re: Is this legal ?
    ... the member and giving you more flexibility in the ... lcc-win32 doesn't accept this code in conforming mode, ...
    (comp.lang.c)
  • Complex number support
    ... or lcc-win32 is missing some basic elements of C99 complex ... int main ... This is with or without the -ansic flag. ... Warning 7.c: complex-7.c: 9 possible usage of operator before definition ...
    (comp.compilers.lcc)