Hi Viktor, Pritpal,
Il 04/02/2009 3.35, Viktor Szakáts ha scritto:
To put it shortly: IMO hbwin should be a pure wrapper for
the Windows API and closely Windows API related features,
nothing more, nothing less. It's also important that
64-bit, Unicode and GCC/MSVC/POCC/OW compatibility be
kept here, and some other general code quality considerations
as well, like safe string operations, ANSI comments, and good
source file granularity.
Ideally I'd imagine below steps to clean up this situation:
1) Remove hbole.lib.
2) Move WIN_*() from GTWVG to hbwin.lib
3) Move WIN_*() from uhttpd to hbwin.lib
4) Disable hbwhat from mainstream builds (move to
examples) and start to move useful, tested and error-free
parts to hbwin.lib.
5) Further cleanup hbwin.lib (naming, better separation
of API, additional convenience functions and classes).
6) Remove hbwhat.lib altogether.
sorry to jump in and probably missing some infos, but only as suggestion
may I propose to adopt this naming convention:
1) replicate, as possible, windows dll api into a single file, i.e.
w_gdi32.c, w_kern32.c (or such similar name) in which we know we can add
API as described in MSDN structure.
2) using, as above, header defines in *.api files (winuser.api, wingdi.api)
3) using, as namespace, WIN_API_*() as pure api wrapper and WIN_*() for
"rearranged" C functions
4) as possible, but has to be well tested, using STRUCTURES as per
Pritpal proposal
Best regards
Francesco
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
