>> I've filed this as: >> http://bugs.exim.org/show_bug.cgi?id=939 >> How about simply forcing C mode for this library in Harbour? >> We're again in a situation where we deviate from standard >> build procedure which just causes us problems, so it seems >> more convenient to do this instead of maintaining local patches. >> What do you think? > > As you wish though PCRE and ZLIB are a little bit specific. > Unlike other external libraries they are referenced from core > code so I would like to keep them working in both C and C++ mode. > Sooner or later we will work on UNICODE support in HVM and it > will be necessary to dig into PCRE much deeper so it's highly > possible that at least for some time we will have to use our > own strongly modified PCRE code which should work in C and C++ > mode. Forcing C mode may strongly reduce the code quality because > C compilers are not such restrictive as C++ ones.
Well, since this is foreign code, we are not the ones responsible for code quality. > One of the most value able part of Harbour is portability. > It can be easy ported to many different platforms and C/C++ > compilers and I would like to keep it for core code. That's fine, but I personally wish not to maintain local patches for non-Harbour code unless absolutely unavoidable or necessary. As soon as we'll have heavy local modification needs we can rethink this, but even then, I'd encourage ourselves to submit all these patches to PCRE project, rather than trying to keep syncing it or creating a fork. But we will see; for now it's impossible for me to see what these local modifications will be and what will be the best thing to do at that time. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
