This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch, libgfortran] PR32784 Using 'CONOUT$', 'CONIN$', or 'CONERR$' , Part 1
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: Jerry DeLisle <jvdelisle at verizon dot net>
- Cc: Fortran List <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 19 Jul 2009 13:41:37 +0100
- Subject: Re: [patch, libgfortran] PR32784 Using 'CONOUT$', 'CONIN$', or 'CONERR$' , Part 1
- References: <4A629FBB.4070005@verizon.net>
Jerry DeLisle wrote:
> I have tested the patch on Cygwin-1.7. I have not conjured up a
> suitable test case since this simply does DOS console I/O. I have
> attached a simple test program that I used.
Well you could always commit that, and the fact that it executes
successfully will mean the device names were at least recognized. Also, since
the test framework I think effectively captures the test output by redirecting
stdout, you could verify that stuff printed to CONOUT$/CONERR$ does *not* end
up in the output and that stuff sent to stdout/stderr does?
cheers,
DaveK