> Przemysław Czerpak wrote: >> BTW I would like to start build tests on different platforms. >> I hope that we will release final 2.0 before Christmas. > > This is perhaps a question to Viktor. When the depreciated function support > expires? Do we have some rules for this?
We have rules for HB_LEGACY_LEVEL2, where we say they gonna be fully removed in next major version, which means whatever version that follows 2.0. > Actually I have a problem with MessageBox() (from hbwin/legacyco.c) it > clashes with my own library, so each time I do free SVN update I should > delete this source C file from Makefile. Legacy support is from 2009-05-13. For these legacy functions I defined no date by myself. Since they are .prg level functions users are probably more sensitive about losing them. I'd personally either opt to drop them after next major version (f.e. 3.0), or, f.e. with hbwin lib we can move them to xhb lib, since their major purpose is to keep compatibility with xhb, because most of these functions came from there originally. We can do the hbwin legacy move even now. The rest, f.e. hbodbc and hbmysql legacy functions can be guarded with HB_LEGACY_LEVEL2, since they are not used by that many users AFAIMC. But, back to your actual problem, you must be using some other legacy functions which makes this file pulled in. IMO you could simply solve your problem by changing this legacy call to the new equivalent, and legacyco.c would not be linked at all. That's the reason I moved these legacy wrappers in separate files in the first place. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
