Well, we can switch to -Wall if that helps finding more potential problems in Harbour. Most of these warnings are known to me and I hope we can deal with it as part of the introduction of (and switching to) our new Harbour types. On many occasions such switch could solve these warnings much more efficiently than just simply suppressing the error (= sweeping it under the carpet) with an explicit cast. Look at the ULONG vs. long vs. size_t problem for example. Or places where a given entity doesn't have a well-defined int size along whole Harbour (GT row/col f.e.).
We have lots of additional similar warnings with msvc64 and we have several type name collisions when using Harbour with certain tools (FreeImage and owatcom for example). There is a lot to do here, and it needs contributors. There are some warnings which I have no idea how to correct, like the FARPROC conversion. Anyhow I certainly hope we can clear these up in the future. Brgds, Viktor On Thu, Apr 16, 2009 at 1:51 PM, Ranier Vilela <ran...@cultura.com.br>wrote: > Viktor Szakáts escreveu: > >> Hi Ranier, >> >> The way to post large files is to upload it somewhere and post a link. >> >> MSVC compiler has lots of known warnings waiting a future cleanup, we're >> using -W4 warning level which is quite picky. >> >> You can override to -W3 to get a "clean" output. >> set HB_USER_CFLAGS=-W3 >> >> Brgds, >> Viktor >> >> On Wed, Apr 15, 2009 at 10:26 PM, Ranier Vilela >> <ran...@cultura.com.br<mailto: >> ran...@cultura.com.br>> wrote: >> >> Hi, >> >> 1. Wich the right way for sending a huge (855 kbytes) of a text >> file to harbour developers list? >> Is result of a full compilation with several warnings from msvc >> compiler. >> >> Some are very interesting! >> >> Best, >> >> Ranier Vilela >> >> PS: Attached does not work, I tried for 3 times. >> >> Ok, Thanks. > > IMO, I prefer the -Wall ;) > > But some warnigs need especialized attention: > > cl.exe -nologo -I. -I../../../../include -Gs -TP -Wall -wd4127 -Ot2b1 > -EHs-c- -MT -c harboury.c -Foharboury.obj > harboury.c > harboury.c(546) : warning C4668: 'YYENABLE_NLS' is not defined as a > preprocessor macro, replacing with '0' for '#if/#elif' > harboury.c(3556) : warning C4668: 'YYLTYPE_IS_TRIVIAL' is not defined as a > preprocessor macro, replacing with '0' for '#if/#elif' >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
