On Wed, 01 Jul 2009, Alexander S.Kresin wrote: Hi,
>> I updated the patch so now LETO can be compiled also by Harbour >> and probably also by old Harbour though I haven't restored wrong >> casting for [const] char|BYTE * strings so C++ some compilers >> may refuse to compile LETO with xHarbour or old Harbour header files. >> With C compilers it should work. > I've noticed this message just now, I'll review the patches today. I've just merge it with you recent leto CVS update. It cleans nearly all GCC/MinGW warnings except few ones which I think you should pacify yourself because they may be source of real errors and I would only hide them. See below. It also updates for UNICODE compilation in windows and cleanes unsigned char * / char * usage what eliminates most of explicit conversions so I was bale to add 'const' to declaration and now compiler can catch and warn in all places where some literal strings are passed unprotected. It should help in detecting possible corruption of readonly area. Current patch in attachment. I'm setting CC to you to avoid repeated work. Please ignore previous patches. best regards, Przemek
leto-cvs.diff.gz
Description: GNU Zip compressed data
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
