On Wed, 23 Jan 2008, Mindaugas Kavaliauskas wrote: > I've just migrated from xHarbour to Harbour in majority of projects. I > remember xHarbour /w3 warnings was completely wrong, but now I've tried > /w3 on Harbour. It works much better - no wrong warnings. It helped to > find one error in code: duplicated data member of class.
The information about duplicated members is really usable. Said that many others do not work or work incorrectly. The Harbour /w4 output is cleaner then xHarbour one because most of messages were disabled or never enabled. > I've just found that these memory leaks are "documented" in the source, by: > /* TOFIX: these allocations causes memory leaks */ > (one place in harbour.y, two places in hbmain.c). I know, I created those TOFIX notes. > This could be easy fixed by: [...] > I understand strong typing should be rewritten, but if we do not disable > /w3, I can commit this change, to avoid long screen of unreleased memory > block log. Please do it. Best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
