On Thu, Dec 16, 2004 at 08:53:32AM -0600, Craig A. Berry wrote:
> The new test 146 has been failing on both VMS and Win32. At least on
> VMS, the failure is because it's not accounting for the newline you are
> guaranteed to get at EOF, and I suspect it's the same issue on Win32.
> After the attached, the test passes on VMS.

For future reference, in these sorts of situations its perhaps better to
use -l to produce more predictable output.


> --- t/op/bop.t;-0     Tue Dec 14 02:09:24 2004
> +++ t/op/bop.t        Thu Dec 16 08:24:18 2004
> @@ -324,4 +324,4 @@
>  
>  # [rt.perl.org 33003]
>  # This would cause a segfault
> -is( runperl(prog => 'eval q($#a>>=1); print 1'), 1 );
> +like( runperl(prog => 'eval q($#a>>=1); print 1'), "^1\n?" );


-- 
Michael G Schwern        [EMAIL PROTECTED]  http://www.pobox.com/~schwern/
5. It is always possible to aglutenate multiple separate problems
   into a single complex interdependent solution. In most cases
   this is a bad idea.
    -- RFC 1925

Reply via email to