Hello Viktor
vszakats wrote: > > * contrib/hbwin/wapi_commctrl.c > * contrib/hbwin/hbwapi.h > ! Fixed to compile under various other win compilers. > ! Added missing WinCE protections. (notice all tools are freely > available to check these and avoid breaking builds) > Added non-WinCE branch to return dummy values. > ! Formatted: (_WIN32_IE >= 0x0300) -> ( _WIN32_IE >= 0x0300 ) > ! Fixed non-ANSI comments. > ! Fixed warnings, and there is still some dubious comversions > in there like HANDLE - HTREEVIEW and RECT passings. I wonder > if it is possible at all to create clean Windows API code. > ; NOTE: Please take care of above stuff, it's not a pleasure > to be the cleaner of such code, but it breaks builds > to it must be done all the time. > ; NOTE: I'd like to recommend adding only Windows API functions > which are available on all Windows platforms (WinCE, > Win64) otherwise it will be more difficult to build > anything portable on top of them. > ; QUESTION: Why many functions are disabled with #if 0? > It appears that there is no proper way to write WinApi wrappers purely based on pointers. Until we come up with official structure support, it is futile to write these wrappers. I wrote these wrappers for one of my projects and posted in SVN with pointer modifications, with a hope these will be useful one day, but probably we should drop them. Please undo this commit as I am away from my dvelopment environments right now. There is no point to keep unsupported code. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/SF.net-SVN%3A-harbour-project%3A-11786--trunk-harbour-tp24497540p24501481.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
