Hi everyone,
supposing that I want to keep code and tests in one single file, is
there a common idiom to do that?
At the moment I'm going with something like:
if $?FILE == $*PROGRAM_NAME {
use Test;
plan 1;
ok foo();
}
but this seem unnecessarily verbose.
Is there some standard idio
On Fri, Jan 05, 2007 at 04:14:27AM +0100, gabriele renzi wrote:
> supposing that I want to keep code and tests in one single file, is
> there a common idiom to do that?
Nice idea!
> At the moment I'm going with something like:
>
> if $?FILE == $*PROGRAM_NAME {
> use Test;
> plan 1;
> ok
On Thu, Jan 04, 2007 at 10:37:51PM +, Jonathan Worthington wrote:
> Lee Duhem (via RT) wrote:
> >This patch suppress some uninitialized value warning in
> >config/inter/yacc.pm when use --maintainer option at configure.
> >
> I'm kinda concerned about what will happen if $3 was 0 (and was me
# New Ticket Created by James Keenan
# Please include the string: [perl #41186]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41186 >
Particle has asked me to consider testing and refactoring
('phalanxing', for short) to
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41187]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41187 >
After update to 16418, test t/examples/past.t failed:
$ /usr/local/bin/perl t/harness --
gabriele renzi skribis 2007-01-05 4:14 (+0100):
> I think it should be possible and nice to use a macro (possibly a
> standard subroutine, I'm not sure) like
> testing {
> ok foo;
> }
> would it make sense or I'm just crazy?
Possible, presumably easy to implement, and a great idea.
I love it!
I propose that we remove the following two lines from the smart match
table in S03:
HashAny hash entry existence exists $_{$x}
Array Any array contains item* any($_) === $x
These are the two lines with Any on the right side. I want to remove
these so that we can
On Fri, Jan 05, 2007 at 08:47:18PM +, Luke Palmer wrote:
: I propose that we remove the following two lines from the smart match
: table in S03:
:
:HashAny hash entry existence exists $_{$x}
:Array Any array contains item* any($_) === $x
:
: These are the two
On Fri, Jan 05, 2007 at 01:40:44PM +0200, Gaal Yahas wrote:
: > I think it should be possible and nice to use a macro (possibly a
: > standard subroutine, I'm not sure) like
: >
: > testing {
: > ok foo;
: > }
: >
: > would it make sense or I'm just crazy?
:
: I like the approach.
I think you
At the moment I'm leaning toward:
$pattern.accepts($thing)
$pattern.rejects($thing)
and going the other way
$thing ~~ $pattern
$thing.match($pattern)
$thing.subst($pattern)
and most generally, something like:
$thing.does($pattern)
$thing.when($pattern)
By the way,
James Keenan wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #41186]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41186 >
Particle has asked me to consider testing and refactoring
('phal
James Keenan wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #41186]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41186 >
Particle has asked me to consider testing and refactoring
('phal
Jonathan Worthington wrote:
I like the look of this, but if I wanted to go about implementing it I
feel I'm kinda short of what that means implementation wise. I'm happy
enough with flattening composition and all that jazz, but a little extra
guidance on what you're expecting to compose into th
13 matches
Mail list logo
