> What32 plus few more classes. > > 3.82 MB on disk size. > > "vouch32" can be "vouch", no problems. > I told that it compiles with current Harbour and > works flawlessly with my production applications. > > I can publish also the way it can be used with any > console application ( on Windows ) just like Clipper, > or other compiler as Xbase++.
I had my share of experiences with WHAT32, and it was the only lib I had to decide to pull completely due to the many problems (and many many lost hours of work), and I could only scratch the surface of the problems, f.e. memory leaks and GPFs or duplicated functionality wasn't even touched, there was also the copyright issue with the headers. It was already a huge impact, even though it was less than 1MB :( And WHAT32 was supposedly working code pulled right from live xhb repository.. It was especially difficult since I was all alone with the effort to take WHAT32 anywhere, nobody seemed interested enough to help. [ So now we develop hbwin lib. ] Pls remember that "working" code has been proven to fail many times here on the various requirements of clean and really faultless code, not to mention when imposed to both Windows and WinCE platforms, all CPU targets (x86, x64, IA64, ARM) and all supported C compilers in all the modes we support in Harbour ([!]UNICODE, [!]WIN32_LEAN_AND_MEAN, C and C++). With all due respect to your work I maintain my opinion to keep it outside Harbour repository, it's much useful for both projects to stay separate. For Harbour I suggest to improve and fix what we have at hand. At the same time I hope to see VOUCH[32] (the name we've heard, and the icon we've seen so many times) in a repository near us ;) Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
