On Mon, Jan 25, 2010 at 7:02 AM, Wormszer <worm...@...> wrote:

Actually my error was strchr returning a char* instead of a const char*.
osolex.l line# 260

Yeah, I believe that's fixed in the patch.

On Sun, Jan 24, 2010 at 3:44 PM, Wormszer <worm...@...> wrote:

I too recieved an error from strcmp in oslex.l/cpp when building with
visual studio.

Visual studio has not deprecated hash_map from what i can tell, but a
boost solution would work there as well.

From what I can tell, the latest visual studio has a native
unordered_map implementation, but my preference for boost is just
because it's consistent across all platforms.

Does the gcc build really generate no warnings, i guess it must not with
the compiler flags to make warnings errors?

Yep.

I just built oslcomp and I get about 3800 warnings, this is displaying all
warnings.

This is to be expected really; all the different compilers have
somewhat different ways of checking for suspicious code, and the
compiler authors have different standards about what they consider
"suspicious" ;-)

~Chris