Viktor, > I'd welcome opinions from everyone.
Personally I don't think we should add every 3rd party library in the market to the Harbour repository. There are endless features out there that are "nice to have", but not every such tool need to have wrapper functions in this project. Look at the size of "core" tree compare with the size and number of files in "contrib". The great part of Clipper was the fact that the basic complier had a huge 3rd party companion market (both free and commercial). It was not integrated into one monolithic product. 3rd party wrote libraries that worked with that compiler and default libraries (plus the C-RTL). Now, in Harbour, instead of the people that write the libraries try to adopt their product to Harbour. The Harbour developers "hunt" for external projects and do the adaption here (as the original lib team might not had even heard about Harbour). I don't think this is good. I know these tools are useful, but the scope is just too huge. And now you propose to add even tighter integration which will force part of Harbour to be updated every time an external library is being updated. Well, it looks like endless task. BUT: As YOU are the one doing most (or all) the cleaning, and if you think this is not a nightmare, and will even cause you less work in the future, go for it. Chen. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
