Hello Viktor
Viktor Szakáts wrote: > > We still have a namspace problem in GTWVG and I'd like to > solve it before we do the release. > > In wvgwin.c there are 93 functions with WIN_ prefix. > > WIN_ prefix is reserved for hbwin library. This is very important > for several reasons, just to name a few: > - Any users reporting a problem, now we cannot be sure > which subsystem is involved. > - Consistency for users: I've made efforts to clean hbwin code > to use pointers. This behaviour is officially associated with > WIN_* and WAPI_* namespaces. So, for users it's very > confusing to have another set of WIN_ functions which are > requiring numeric pointers. All this will not help Harbour > Project to be recognized as a trusted developer when it comes > to winapi. Which may nil the efforts of hbwin. > - Consistency for us developers: We can accidentally > introduce a colliding name which may only be found when > it's too late (already happened). > > I know you're busy with hbxbp, and if you agree on the > fundamentals I can do the renaming in GTWVG. At the > same time I'd like to move WVG_* functions in this same file > to wvgwing.c, this will probably help in the future. > > I'll publish a batch which will make it easy to convert any > app code relying on these functions. For local apps it's > also a possibility to add wrappers, but this code should > only be used locally. > > Eventually I still hope the generic bunch of these functions > will be cleaned (UNICODE, WinCE, x64, general review, > pointer param usage are the main tasks) and moved to hbwin. > My real-time applications ( in production ) are solely based on GTWVG. Let me do this. I concentrate on GTWVG for this week. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/GTWVG-and-WIN_-namespace-tp24069088p24074469.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
