Hi
Viktor Szakáts wrote: > > What is the situation with wincallb.c in GTWVG, > I've seen you've added clean callback support to GTWVG, so > the question is whether we can now remove the old one > in wincallb.c? The old one still seem to be used from some > places so I couldn't do it. > > [ The old one is non-portable, x86 CPU specific ASM/binary > code. Generating lots of valid warnings, too. ] > > There are also a few functions declared in GTWVG > in the WAPI_* namespace, I think they should be > renamed to some local names. > I will be cleaning parts probably today. Which functions in WAPI_* namespace you are referring to ? Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/GTWVG-and-wincallb.c-%2B-WAPI-tp22358281p22358543.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
