I've gotten absolutely no response about Test::Legacy. Is anybody
using it? Anybody tried migrating old Test.pm based tests with it?
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
I'm crazy but I get the job done.
On Dec 20, 2004, at 6:41 PM, Michael G Schwern wrote:
PS Somebody should drag autrijus into this.
I'll try to grab him on IRC in the morning...
Regards,
David
My Official Policy on this is now to let people who actually understand
character encodings to work it out and just wait for a patch.
PS Somebody should drag autrijus into this.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
We don't know. But if we did, we would
On Dec 20, 2004, at 6:19 PM, Michael G Schwern wrote:
Is there a module or function in Perl that can provide this
information?
Why does it matter what it was set to before? I'm always going to be
shoving text out through this filehandle.
It matters because if I'm using Big5 in my module, I *don't
On Mon, Dec 20, 2004 at 06:20:41PM -0800, David Wheeler wrote:
> If not, another option is to add a binmode option to Test::Builder (and
> the modules that depend on it). So you could do something like this:
>
> use Test::More tests => 6, binmode => ':utf8';
>
> Thoughts?
Again, this is not s
On Mon, 2004-12-20 at 18:20 -0800, David Wheeler wrote:
> If not, another option is to add a binmode option to Test::Builder (and
> the modules that depend on it). So you could do something like this:
>
>use Test::More tests => 6, binmode => ':utf8';
>
> Thoughts?
I'd rather override Test:
On Dec 20, 2004, at 6:13 PM, David Wheeler wrote:
If there was a way to tell what mode was on STDERR before you duped
it, you could just set it to the same. Something like:
my $mode = what_binmode(STDERR);
my $fh = $builder->failure_output;
binmode $fh, $mode;
Is there a module or function
On Mon, Dec 20, 2004 at 06:13:54PM -0800, David Wheeler wrote:
> >Test::Builder should do something like this internally, its not like
> >anyone's
> >going to drive binary data through a TB filehandle. The question is
> >how does one do it without breaking older perls?
>
> If there was a way to
On Dec 20, 2004, at 6:06 PM, Michael G Schwern wrote:
use Test::Builder;
BEGIN {my $fh = Test::Builder->new->failure_output; binmode $fh,
':utf8';}
Test::Builder should do something like this internally, its not like
anyone's
going to drive binary data through a TB filehandle. The question
On Mon, Dec 20, 2004 at 04:50:57PM -0800, Ovid wrote:
> And looking at line 1005:
>
> sub _print_diag {
> my $self = shift;
>
> local($\, $", $,) = (undef, ' ', '');
> my $fh = $self->todo ? $self->todo_output : $self->failure_output;
> print $fh @_; # here there be smart quotes
=head1 Announcing the Do-It-Yourself Phalanx 100!
The Phalanx 100 is a list of the "top 100" modules on CPAN, and by
extension, those that should have the most attention paid to them by
the Phalanx project.
The first time I generated the P100 was over a year ago, and things
are old and stale. Di
=head1 Announcing the Do-It-Yourself Phalanx 100!
The Phalanx 100 is a list of the "top 100" modules on CPAN, and by
extension, those that should have the most attention paid to them by
the Phalanx project.
The first time I generated the P100 was over a year ago, and things
are old and stale. Di
Hi all,
The following code:
use utf8;
use diagnostics;
BEGIN {binmode STDOUT, ':utf8';}
use Test::More tests => 1;
# those are smart quotes
diag "This is a \x{201c}test\x{201d}";
ok 1;
Produces the following error message:
1..1
Wide character in print at /usr/local/lib/perl5/
13 matches
Mail list logo
