I would add also HB_PP_MULTILINE_STRING.
Without it valid code of betaX would not compile.

Doesn't this break compatibility?

Back to HB_INCLUDE_WINEXHANDLER for a sec, IMO we
should enable the Win GPF handler by default (without
option), and make it an option to pop a MessageBox()
in case of error, but by default, I'd always make
Harbour write the GPF info into a .log file similar
to fm.log, this way it wouldn't disrupt non-interactive
application, yet the valuable GPF info wouldn't be lost.

Any opinions?

I vote a 'no' for xhb to be packaged in default build, as
it quite effectively pollutes the Harbour include dir right
now. If this is indeed such important for most ppl I'll
consider removing most xhb compatibility headers, leaving
only hbcompat.ch, which should BTW be renamed to xhb.ch,
(hbcompat is too generic).

So we can delete all the DIRS from contrib/Makefile and use only
HB_CONTRIBLIBS envvar.

Well, yes, if we don't want any default choice of contribs.
Another option would be to remove contrib from /Makefile,
so that building contribs needs another build step. That's
how non-GNU make files work now. I have no preference here
this time.

Brgds,
Viktor

_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to