Current hbmk2 behavior is OK for me - thank you very much and I
think
we should only add support to "inherit" C++ mode from Harbour build
settings.
I'd resist here. Certainly not a good idea on non-*nix
(additional question: should watcom and msvc built hbmk2
compile in C++ mode by default too?), which makes it rather
hm. i haven't thought about this. you may be right.
maybe it's just gcc/g++ that's the exception here, wrt how it handles
c/cpp mode linkage? sunpro seems to be able to deal with it, but i
don't know others. if it's just gcc, then it may worth putting in a
quirk for it.
This is what I proposed in my last answer to your mail also.
Seems that we'd need to link in stdc++ (or supc++) for all
gcc compilers. Questions: Which one? Does it make any harm
for scenarios when this lib isn't actually needed (pure C)?
By some info found on the net supc++ is a subset of stdc++,
and it can be linked statically. It's rather a hunch than
an educated opinion, but linking supc++ seems to be a better
fit, and I'd guess this wouldn't make any harm when added
to liblist of non C++ programs (few simple tests is mingw
confirmed the latter).
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
