[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [ANN] Lua 5.2.0 (work1) now available
- From: steve donovan <steve.j.donovan@...>
- Date: Sat, 9 Jan 2010 09:39:09 +0200
2010/1/8 Ignacio Burgueño <email@example.com>:
> error: previous declaration of 'LoadStringA' was here
> lundump.c:76: error: conflicting types for 'LoadStringA'
The problem here is that Windows uses a nasty preprocessor hack for
functions which have ASCII and Widechar variants. So there's a:
#define LoadString LoadStringA
in the headers, assuming this is a ASCII build.
So, #undef LoadString is one fix. But surely camel-case identifiers
like this are not otherwise found in the Lua sources? Windows people
instinctively avoid them for the above reasons. Seems like a rename
would solve the problem cleanly.