I am trying to compile a project with VC++7 in a Win32 project. There are no errors, but a lot of warnings. Like:
c:\Development\parser\test1\test_scanner.hh(241) : warning C4290: C++ exception specification ignored except to indicate a function is not __declspec(nothrow)
and
c:\Development\parser\test1\test_scanner.hh(233) : warning C4267: 'argument' : conversion from 'size_t' to 'int', possible loss of data
Is it Bad? Solutions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have NO idea what the first warning is trying to say (haven't used VC++ since old 5.0), but i don't think it's bad. Same for the second one (though, can you send me the surrounding lines, i could add an explicit cast just to make the compiler shut up). I expect the parser to work despite those warnings (and it probably does). Let me know
Alec.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
VC6 will generate the same warning about exception specifications. Basically, they are ignored and the function can still throw any exception. Maybe this has been fixed in .NET 2003.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to compile a project with VC++7 in a Win32 project. There are no errors, but a lot of warnings. Like:
c:\Development\parser\test1\test_scanner.hh(241) : warning C4290: C++ exception specification ignored except to indicate a function is not __declspec(nothrow)
and
c:\Development\parser\test1\test_scanner.hh(233) : warning C4267: 'argument' : conversion from 'size_t' to 'int', possible loss of data
Is it Bad? Solutions?
I have NO idea what the first warning is trying to say (haven't used VC++ since old 5.0), but i don't think it's bad. Same for the second one (though, can you send me the surrounding lines, i could add an explicit cast just to make the compiler shut up). I expect the parser to work despite those warnings (and it probably does). Let me know
Alec.
VC6 will generate the same warning about exception specifications. Basically, they are ignored and the function can still throw any exception. Maybe this has been fixed in .NET 2003.