Hi Viktor,
Il 04/02/2009 10.14, Viktor Szakáts ha scritto:
In contrary, I'm happy you've joined the thread :)
Thanks
2) using, as above, header defines in *.api files (winuser.api,
wingdi.api)
Here I don't agree, because usually I find it better
to use standard extensions, so if something is a
header I think we should stick with .ch, .h.
[ .api is reserved for Clipper legacy C headers,
and besides that, it's unclear by the name whether
they are meant for C or .prg code. ]
Since original Windows headers are a relatively
big mess, maybe it would be better not to replicate
it in hbwin.lib, but rather use one unified version,
hbwin.ch and hbwin.h. This is what we already do now.
Ok for using *.ch, *.h, but if it is possible, to see immediately where
put a new addition, as per c api file I would like to mantain ms naming
convention, so for me it will be better to use, f.e., w_winuser.ch or
winuserapi.ch
If whole group agrees, and if that can help on the
file naming situation, we may lift the 8.3 chars naming
restriction for hbwin.lib. It's important to see however,
that DOS builds will be unable to compile hbwin.lib,
so despite any stubs implemented, DOS apps will
have to do without hbwin.lib functions, and they'll
definitely need to guard them with __PLATFORM__WINDOWS.
it will be good
3) using, as namespace, WIN_API_*() as pure api wrapper and WIN_*()
for "rearranged" C functions
Good idea. Maybe WINAPI_*() would be even better.
ok
4) as possible, but has to be well tested, using STRUCTURES as per
Pritpal proposal
Yes, well tested, portable, MT ready, alignment independent,
free from accessing Harbour internals, etc. IOW, if it can be done
in core quality, it's okay, if not however, it wouldn't be good to
build the whole lib upon it.
yes, but should be verified because this will give a useful tool more
readable and more near to ms approach and it can make easier to move ms
code, IMO.
Best regards,
Francesco
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
