> > I agree with your viewpoint but at the moment, or until > we create a common library to be used by all libs, I would like > if you change WIN_ * with something else. > > Perhaps I cannot change my whole code as I use hbwin.lib also.
You can continue to use latest version which doesn't have the renaming, until you change your source. Or even the last stable version from 1.0.1. There wasn't really that much change there since. I've peeked into gtwvg, well wvgwin.c has a mixture of WVG and WIN functions which should IMO be separated into distinct source files. The WIN part of it should ideally be moved to hbwin.lib, but first fixed for 64-bit/WinCE/Unicode (if needed). BTW, we're talking about three functions, AFAICS: WIN_MULDIV() (exact same code in both libs) WIN_RECTANGLE() WIN_SETBKMODE() I'll commit something for the latter two. Note GTWVG came into existance much prior to HBWIN. hbwin is a generic Windows API wrapper library, while GTWVG is special GUI lib with mixed in Windows functions, in my view the priority is clearly to the generic lib. hbwin came to light as a result of separating Windows specific stuff from core, and gathering Windows API pieces scattered around in small contrib libs. I see no point in arguing who was here first, I certainly got to know about GTWVG much later, not that this would matter. I'd say let's try to get rid of what's not needed, and try doing the Windows API wrappers in a generic way, so that they become useful for everyone, then _reuse_ it, instead of reinventing it for every contrib which needs the Windows API. Brgds, Viktor
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
