Hi Przemek,
On 2008.05.07., at 12:46, Przemyslaw Czerpak wrote:
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
relying on this specific detail.
What do you think?
It was Clipper CT3 compatible behavior implemented in a why
which was not breaking any existing Clipper code. This modification
broke my CT3 DOS code which uses CTWIN. Please revert it too because
it breaks existing Clipper code which uses CTWIN form CT3.
How is this implemented in Clipper + CT3 DOS?
As far as I could see MaxRow() passes down the call
to _gtMaxRow(), which returns the value without any
special tricks in Clipper.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
