There is also a workaround where you #include external
.c code inside BEGINDUMP/ENDDUMP. So that you can switch
between both methods. This adds some more complexity,
though.
He cannot. As I said in xHarbour this feature does not work
correctly and #include "<file>.c" inside BEGINDUMP/ENDDUMP
is yet another example where it does not work. Just simply
xHarbour does not know anything about dumped code and does
not recognize C preprocessor directives so if you make it
then you will have exactly the same results in Harbour now.
I see. Only real separation is left then, using "__" function
name prefix (or doing everything in C).
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
