>>> To be on the quicker side, and if it can be acieved easily, >>> can you provide functionality to call Harbour.exe for each souce >>> separately controllable through some switch, i.e., -componebyone=yes. >> >> No sorry, I'd like to find the real solution. >> > > Any clues?
To me it looks like a regular problem, not some kind of bug. > Also consider that hbIDE will be using -xhb mode also. If you think hbmk2 is the suspicious piece one here, simply try the harbour cmdline (printed by -trace) directly. If it behaves differently, it's a HB_COMPILE() function problem, if not, look closer into Clipper/Harbour behavior to find out why it's behaving like it does. Another possibility is some Clipper incompatible behavior of xhb which masked some problems in your code thus far. > So solution should address this situation also. I mean it will > be difficult to make changes in compiler code in older xHarbour, IMO. I maintain it's not a hbmk2 problem. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
