--- [EMAIL PROTECTED] wrote:
> 27/02/2004 10:30:22, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>
> >[EMAIL PROTECTED] wrote:
> >
> >> Compiler version:
> >>
> >> Microsoft (R) 32-bit C/C++ Standard Compiler Version 13.00.9466 for
> 80x86
> >
> >Thanks update.
> >
> >
> >> t\op\00ff-dos.t 255 65280 2 4 200.00% 1-2
> >
> >Strange
> >
>
> I've sent a patch that makes this problem "go away", though I do not
> understand
> the cause. The 'fix' was to c&p the entire script into a new file, save it
> using
> "codeset=ANSI" & "filetype=unix", overwriting the original.
>
> Then the test completes without error.
>
> Running "cvs diff -u -b" is the (attached)patch I've sent. I'll leave it to
>
> others to interprete the diff.
That defeats the whole point of 00ff-dos.t, which is to make sure parrot can
deal with lines ending in \r\n. IMO what should be done is to use \r\n in a
quoted string, instead of having the .t itself be \r\n (since that is what
was causing the problems, getting translated into \r\r\n). (See the
attachment for what I mean)
__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
#! perl -w
# Copyright: 2001-2003 The Perl Foundation. All Rights Reserved.
# $Id: $
=head1 NAME
t/op/00ff-dos.t - DOS File Format
=head1 SYNOPSIS
% perl t/op/00ff-dos.t
=head1 DESCRIPTION
Tests file formats.
=cut
use strict;
use Parrot::Test tests => 2;
my $code = qq(print "ok\\n"\r\nend\r\n);
output_is($code, <<'OUT', "fileformat dos");
ok
OUT
$code = qq(print "ok\\n"\r\nend\r\n\cZ\r\n);
output_is($code, <<'OUT', "fileformat dos w ctrl-z");
ok
OUT
