I'm not a DOS/Windows user and I expect that when I redirect stderr
to file then for clean builds without any warning this file will be
empty just like in all other compilers I'm using. I know that due to
missing stderr redirection in pure DOS command.com DOS compilers were
using many different hacks (f.e. reverted stdout and stderr) but It's
not our problem and I do not want to inherit it in normal environments.
So please revert this modification.
Well, for me it's not a problem.
Notice however that by using -q/-q0 the whole problem disappears,
as none of these messages would appear on any outputs, and
this is what I expect to happen in most "advanced" build environments
(I may be wrong though). So, IMO, -q is what you need, rather than
1> relying on this specific detail.
What do you think?
Hi,
I do not remember the date, but we've already had discussion on exactly
the same topic some time ago.
I think #ifdef guarded platform dependent behaviour is the only
solution, that will satisfy both DOS and Linux users.
Best regards,
Mindaugas
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
