> > I thought that only standard C language header files needed <>. Can you > address me to an official docs that explicitly state something different? > Or, from where did you read that <> can be used for non-standard C language > header files too?
http://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html http://msdn.microsoft.com/en-us/library/36k2cdd4(VS.71).aspx If you're still unsure, just look around on any well known OSS projects, or MS source code (the CRT for example), or even official MS Windows headers to see how they #include other Windows headers. > Only HB_OS_WIN_32 has been changed to HB_OS_WIN, >> and HB_OS_WIN_32_USED has been changed to HB_OS_WIN_USED. >> > > Ok. The following sample: > > #define ES_PASSWORD 32 > #define ES_PASSWORD 32 > > > FUNCTION MAIN() > > RETURN NIL > > shows: > > Warning W0001 Redefinition or duplicate definition of #define ES_PASSWORD > > that's perfectly correct. But the compilation is aborted using the > following compiler switches: > > SET HARBOURCMD=/a /es2 /gc0 /m /n /q /w > > How can I instruct the compiler to continue the compilation for this > particular kind of warning? In xHarbour I use > > /w2 /wb- You should remove /es2 switch if you don't want warnings to stop your build process. I don't know exactly what it does, but Harbour surely doesn't support /wb-. Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
