On Mon, 12 Apr 2010, Szak�ts Viktor wrote: Hi,
> Thank you very much. > Harbour standard warning level was not enabled > to avoid watching the large amount of warnings > 3rd party sources are usually causing. > > I know they can be fixed with local patches, but > IMO minimizing number of local patches is a higher > level goal than the current problem when lack of > strict warning causes problems after an update. Not in this case. These warnings were caused by very serious bugs. If I wouldn't tested it then probably we released wrong binaries. Working code is much more important then pacifying warnings. I can leave with warnings but broken binaries are useless for me. > Now I'm getting attached warnings with msvc, bcc > and pocc. (mingw is clean) BCC and POCC does not fully recognize old style function declarations so in this case they can be generat wrong code. Looks that MSVC warnings can be ignored. > Maybe msvc ones can be suppressed with a #pragma? and setting _CRT_SECURE_NO_WARNINGS. Seem that all can be done in zutil.h and gzguts.h. BTW this version does not set -DZLIB_DLL when compiled as dynamic code. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
