yet, I've attached a copy. Feedback welcome.
Internally it uses the following:
'JSON' => 1.00,
'Test::Differences' => 0.47,
'Test::Simple' => 0.62,
'Test::Tester' => 0.103,
Cheers,
Ovid
--
If this message is a res
m sure that the incidence of silly errors
> in distributions would decrease after adding this test. ;-)
Oh, great. You want to ensure I never release another module. Thanks.
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to the l
ve dropped Test::Differences
"eq_or_diff" and just used the "is_deeply" function from Test::More,
but when working with large data structures, there's just no comparison
between the two. I suppose I could make Test::Differences optional and
fall back on is_deeply if they don't h
s more appropriate with helicopters, though, white or
> red?
I'd recommend a nice glass of Cigar Volant
(http://www.strangehorizons.com/2005/20050905/lucianovic-c.shtml)
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questi
t requires *and* what it provides. Are Perl 6 roles
really going to blindly export everything they contain? This seems a
serious mistake. I didn't see anything addressing this issue in
http://www.perl.com/pub/a/2004/04/16/a12.html?page=12
Cheers,
Ovid
--
If this message is a respons
0.21/index.html
I've been using it and once you get it set up, it's fairly straight
forward. You can see a sample in my journal:
http://use.perl.org/~Ovid/journal/27229
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to t
--- Mark Stosberg <[EMAIL PROTECTED]> wrote:
> > http://openjsan.org/doc/t/th/theory/Test/Simple/0.21/index.html
> >
> > I've been using it and once you get it set up, it's fairly straight
> > forward. You can see a sample in my journal:
>
I've wondered about this myself. I've taken over Class::Trait but I
can't take ownership of the RT requests.
Cheers,
Ovid
--- "Christopher H. Laco" <[EMAIL PROTECTED]> wrote:
> When one person takes over the module of another on CPAN via co-maint
> a
>
strong typing, we may still have something
good, but it won't be the relational model.
Of course, all of this would put us on the doorstep of logic
programming but, if I recall correctly, a decision was already made
that Perl 6 wouldn't be delayed for its inclusion. A sad, but
necessar
. Otherwise, into
> C-land you will go, my son!
I'm not entirely sure, but I think we agree here. You have to have, at
minimum, one selector for each new datatype if for no other reason than
to cast a string to your new data type. Otherwise, your data types
would only be constants because
d.
This would make this far more flexible than simply an SQL tester.
Thoughts?
I'm thinking a name like Test::ControlWhitespace.
Also posted to http://use.perl.org/~Ovid/journal/28819
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to
e that into Test::Harness and allow folks to provide their
own grammars and thus structure the output to better suit their needs.
Of course, I would like a Ponie with that, too).
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to the
o better suit their
> needs.
>
> Patches less welcome! :-)
You're hurtin' me, Andy, you're hurtin' me ;)
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
y Mac where the STDERR and STDOUT don't line up.
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
as a "Perl only"
thing, I might (might) be inclined to argue the point, but even then
it's questionable. As a language-independent tool, an API is silly and
I'm a fool for shooting my keyboard off for thinking only about the
implementation problems as opposed to its benefits.
Ch
so, TAP needs to be versioned
and we need to figure out how to accomodate that. Also, how do we want
to handle got/expected failure information in Java or C? There are
pretty rich data structures we could put out there and YAML might help.
That would also likely simplify a parser.
Cheers,
Ovid
--- demerphq <[EMAIL PROTECTED]> wrote:
> On 4/19/06, Ovid <[EMAIL PROTECTED]> wrote:
> > to handle got/expected failure information in Java or C? There are
> > pretty rich data structures we could put out there and YAML might
> help.
> > That would also l
--- Ovid <[EMAIL PROTECTED]> wrote:
> > If you mean you want pluck YAML test results from a noisy input
> > stream I'd say youd probably be wrong.
Naturally, I forgot to include the most compelling argument. The
"noisy input stream" is noisy only because we'
umber, description)?;
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
Based on what I've gleaned from
http://search.cpan.org/~petdance/Test-Harness-2.56/lib/Test/Harness/TAP.pod#Diagnostics,
here's a first pass at an EBNF grammar for TAP. Note that it's
incomplete, but it should be a good start for folks to at least think
about this.
Cheers,
Ovid
ing more along the lines of ">" or "*" to
make it more visually distinctive, but backward compatibility is a
glorious thing. I don't mind "##".
Anyone else?
Cheers,
Ovid
--
If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
f knowing what the programmer and you *can't* handle
diag correctly if you can't disambiguate it. This is another reason
why writing automated tools for TAP is problematic. There's more stuff
folks would like to do and we need these issues resolved to make those
things happen.
Ch
lines OR
> exclusively Win32 newlines.
Sounds like a good idea, but what about strings? You'd need to mask
those out prior to the test, wouldn't you? And if they were multi-line
strings, you'd need to mask 'em out with the right type of ending
(unless PPI were being used).
This seems to work for me:
pugs -e 'say (1,2,3).join("|")'
1|2|3
Or even:
pugs -e '(1,2,3).join("|").say'
1|2|3
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the l
er version, I'd love to see it.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/--
my %buckets = (
'w' => {
'
rg_for {
for 0 .. $arg_for{'count'} -> $index {
$arg_for{'array'}.push($index * $arg_for{'scale'});
}
}
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
- Original Message
> From: Larry Wall <[EMAIL PROTECTED]>
>
> You should not need "my" on the right side of a ->. Also, you should
> be able to write $arg_for for constant subscripts.
Thanks! The revised script is below for those who are interested
uot;int" and "array" stuff as comments right now,
though I could be mistaken.
Cheers,
Ovid
o work there? You're accessing an array, not a hash.
> I assume all those temporaries that I cleaned out were there for
> speed, in which case this will run slower, but they were too
> unsightly to keep around.
Yeah, that's why they were there. However, the ($x, $y, $z).sum > $target is a
much more useful performance hack, so you could get rid of the temporaries.
Cheers,
Ovid
designing and implementing Perl6 (gush, gush,
gush). I was leaning away from Perl5 due to its limitations, but now I'm here
to stay. I am supremely confident that Perl6 will be a hugely popular language
simply based on its merits, not marketing.
Cheers,
Ovid
Sheesh. I type things too fast and then I see the horrifying typos I've made
(blush)
- Original Message
From: Ovid <[EMAIL PROTECTED]>
> do things that is hard to do in other languages.
"do things that *are* hard to do in other languages"
> Perl6 not onl
- Original Message
From: David Romano <[EMAIL PROTECTED]>
> > duplicate results and this is almost always wrong. (See
> > http://use.perl.org/~Ovid/journal/28378
> > for an SQL example of this problem).
> I re-read your journal entry and comments (I had re
Larry pointed out that this topic is better suited for perl6-language instead
of perl6-users, so I'm forwarding this along. Feel free to exercise your
"delete" key.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questi
ee lines from Acme::Code::Police:
$trick_that_naughty_cpants_thingy_into_thinking_I_use_strict = <<'Ha, ha!';
use strict;
Ha, ha!Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
that also makes all her modules phone home
> at install time.
Huh? Can you post an example? The logical spot for having the module "phone
home" would be in the Makefile.PL. I also glanced at some tests, but didn't
see anything there, either.
Cheers,
Ovid
-- If this message
On a related note, if anyone does want to build a P6 Wiki, you might consider
building it on top of WWW::Kontent (http://search.cpan.org/dist/WWW-Kontent/),
a Perl6 CMS (Content Management System) that BrentDax wrote.
Cheers,
Ovid
-- If this message is a response to a question on a mailing
;t know how their monads work or if they would be
applicable :)
> There's some information about this in S05, with more info promised:
> http://dev.perl.org/perl6/doc/design/syn/S05.html#Matching_against_non-strings
Ooh, looks promising. In that scenario, is a hash viewed as an array
ak for Audrey, but she was quite
willing to hand out committer bits and I suspect she'd be happy to have more of
the cookbook fleshed out. We need it very badly!
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
We
Michael,
I assume this is just an attempt to learn Perl6 and not to write a serious CGI
parser? Assuming it's the former and not the latter, I don't really have much
to comment on, though there are a few things I would change.
Cheers,
Ovid
-- If this message is a response to a que
- Original Message
From: Michael Mathews <[EMAIL PROTECTED]>
On 30/05/06, Ovid <[EMAIL PROTECTED]> wrote:
> > I assume this is just an attempt to learn Perl6 and not to write a serious
> > CGI parser?
> > Assuming it's the former and not the
can be hacked up on the fly.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
call having used GDBM_File. Perl6 without a robust HTML
parser would be quite limited for me, though I'm sure one will be ready soon.
Cheers,
Ovid
come up with a solid set of contest rules, TPF can
consider whether or not we can officially run the contest. It sounds like a
nice idea, I just don't know what's involved.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up quest
ad a use_ok test fail but I had so many intervening tests pass that
this scrolled off the screen by the time I got down to my failing tests. It
took me a long time of debugging and calling over other coworkers before
someone spotted that the use_ok was failing.
Cheers,
Ovid
-- If this message i
ite.
Cheers,
Ovid
# got: '3'
# expected: '4'
#> this is diag output
That would be easy to parse, should be trivial to implement and, I suspect, be
backwards compatible.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up qu
ed to ensure that the rest of the behavior is unchanged).
Cheers,
Ovid
as I don't recall hearing any
feedback as to whether or not such a feature would be incorporated.
And while we're at it, another "non-bug" but definitely useful feature out be
for TAP output to have a version number, but that's another story ...
Sorry for the line noise
Hi all,
I would still like to be in a position to write a grammar for TAP, but I've
heard no answers to my questions. Should I assume that a formal grammar is not
wanted/desired at this point?
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
f
r for it, but the grammar can easily
produce some output which doesn't make sense. Thus, I'm stuck in the awkard
position of needing fundamental issues resolved before I can proceed in a
confident manner.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, pleas
tter would allow a simple test of the
TAP version and allow the proper grammar to be loaded rather than use
heuristics to guess what version is allowed.
Cheers,
Ovid
- Original Message
> From: chromatic <[EMAIL PROTECTED]>
> > On Monday 03 July 2006 09:12, Ovid wrote:
> > I am tempted, but there are some problems with parsing TAP output as it
> > currently stands. I can write a grammar for it, but the grammar can easily
&g
all
> > we need is for those officially supporting/maintaining TAP to say
> > "make it so".
> What community do you program for? Just do it, man. Get approval /
> fix it later.
Doing it now. Tougher than I thought! Due to some weird semantics involved,
I've already jettisoned HOP::Lexer and have rolled my own :(
Not sure when it will be done.
Cheers,
Ovid
s merely a
protocal and where it gets written to/read from should be irrelevant.
Mandating that would only impose extra overhead.
Cheers,
Ovid
arser = TAP::Parser->new({
newlines => 1, # add newlines to output
version => $optional_version_number
});
$parser->parse($tap); # croaks if it can't
print $parser->plan;
foreach my $line ( $parser->test_lines ) {
print $line;
}
I'm sure there'
ription;
print $test->directive;# TODO or SKIP data
}
You can download it from
http://users.easystreet.com/ovid/downloads/TAP-Parser-0.01.tar.gz
It'd be awfully swell if you can feed it a bunch of TAP output so I can see
what if fails on. Kibitzing is also encouraged, tho
erl community with the most
experience in a given area know what they're talking about. Maybe that's not
the best approach, but sooner or later we have to trust *someone's* judgment.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
- Original Message
From: Michael G Schwern <[EMAIL PROTECTED]>
On 7/4/06, Ovid <[EMAIL PROTECTED]> wrote:
> > Because we're discarding anything which does not look like a plan or a test
> > line
>
> Don't discard them, just pass them thro
- Original Message
From: Ovid <[EMAIL PROTECTED]>
> Also, since I had not seen the TAP::Harness work before, I didn't
> know that a separate parser was already being planned. My only
> motivation for writing TAP::Parser was my assumption that it was
> need
u think how much time and effort was put into researching and
preparing the Artistic 2 license and it got a fair amount of pushback on it,
why on earth would anyone decide to switch to a different license just because
you want them to?
It ain't gonna happen.
Cheers,
Ovid
-- If this mess
t know if that would bug folks,
though.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
- Original Message
> From: Nik Clayton <[EMAIL PROTECTED]>
> Ovid wrote:
> > I'm perfectly comfortable with this idea, but what I'm trying to figure
> > out then, is the namespace for my parser. It's a TAP parser, after all.
> > Any sugge
s of test behavior, the shouldn't that be the following?
Any text after the test number but before *an unescaped* # is the description
of the test point.
Example:
TAPx-Parser $ perl -MTest::More=no_plan -e'ok 1, "# TODO annoy perl-qa"'
ok 1 - \# TODO annoy
if there's additional output and spit out a different warning?
Should it just treat it as a "Bail out!" line and continue parsing like normal
and let the code using the parser handle that?
if ( $test->is_bail_out ) { ... }
Cheers,
Ovid
-- If this message is a respon
Hi all,
The next version of my TAP parser is at
http://users.easystreet.com/ovid/downloads/TAPx-Parser-0.02.tar.gz
It's still not complete, but it's a lot further along than it was. Some notes
from Changes:
0.028 June, 2006
- Moved some lexer responsibility to
nsensitive to maintain backwards
compatibility with Test::Harness, why wouldn't we keep the escaping for the
same reason?
Cheers,
Ovid
ing _two_
> "Bail out!" lines.)
I think I will make this configurable so that you can continue after a "Bail
out!", if explicitly requested, though if someone really meant to bail out, the
rest of the data would be questionable, though if we're just checking TAP for
validity, I can see your point.
Cheers,
Ovid
- Original Message
From: Ian Langworth <[EMAIL PROTECTED]>
> This is cool, Ovid! I think you're definitely on the right track.
Thanks!
> Thoughts:
>
> - I'd like an option to automatically s{ \A \s* - \s+ }{} all test
> descriptions. I bet a lot of
! # SKIP should never be "not ok"')
- VMS 'not' and 'ok' on separate lines?
Currently the lexer cannot handle this. Should it?
Anything else?
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
eport with [EMAIL PROTECTED] and Robert had to diddle the database to get me
sorted.
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
way, is "not ok" and a skip directive illegal? I assume so and it
should be marked as a parse failure)
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
t;?
I like "pitched" and "caught".
... silence ...
*cough*
Cheers,
Ovid (for Larry's sake, no I'm not serious!)
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
inalize;
foreach my $result ( $parser->results ) {
if ( $result->is_test && $result->failed ) {
my_parser( $result->diagnostics ); # whee! We don't care what it does
}
else { ... }
}
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
ide from the fact that many languages are already using the TAP protocol and
we'd create something they *don't* use, what happens when my 4,000 test lines
all of a sudden become 16,000 test lines because the format has been changed?
*falls over dead*
Hugs,
Ovid
ough it parses the test results directly and then outputs TAP (if I recall
correctly).
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
Aargh! It gets annoying that the reply goes directly to the author rather than
the list.
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
- Forwarded
t:
1..1
# No tests run!
I don't particularly like that this is a silent failure, but I'm not sure of a
robust way to fix that. In any event, I reread the docs a couple of times
before I realized I was being stupid. That suggests to me that this little nit
could be improved.
Ch
- Forwarded Message
From: Ovid <[EMAIL PROTECTED]>
> I have returned to working on the tap parser and stumbled across this
> irritation:
>
> #!/usr/bin/perl
>
> use Test::More tests => 1;
> SKIP: {
>skip "I'm lazy and don't wanna r
dated to indicate that the skip
message must not consist solely of a positive integer, then we're OK. Will
that break anything out there?
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Program
accept a test description?
can_ok cannot accept a description because it accepts a list.
isa_ok can *sort* of accept a description which is why I often do this:
isa_ok $object, 'Foo::Bar', '... and the object';
And the output reads:
ok 7 - ... and the object isa Foo::
, $description;
skip $number, $description;
Just doing this:
use Tests;
Would import the Test::More equivalents.
Thoughts?
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http
- Original Message
From: Michael G Schwern
On 7/15/06, Ovid wrote:
> > Just a thought:
> >
> > use Tests qw/
> > Exception
> > Differences
> > /;
> >
> > Have it import those modules and check for sub conflicts.
ocus on the ease-of-use combined with the
flexibility we need. Using a hashref to enforce named parameters gives us
flexibility, but certainly not ease-of-use.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the
focusing on issues like this is a good thing. For example, what could
be done in TAP::Harness to improve the reporting on line numbers? That alone
would be a nice benefit for folks.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
fol
Hi all,
OK, so I haven't gotten to my 0.10 roadmap yet, but the next version of my TAP
parser is at http://users.easystreet.com/ovid/downloads/TAPx-Parser-0.03.tar.gz
A variety of the changes listed below are precursors to allowing streams to be
handled correctly. Feedback is highly s
nks
have to be "complete". In other words, if I have a "got" in one chunk, having
the "expected" in the next chunk makes it a bit more difficult to handle
(though not insurmountable). However, depending upon how buffering is handled,
I could see this condition aris
TailChasing | Scratch;
Should that be the following?
$fido does Sentry & Tricks & TailChasing & Scratch;
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
rl6/doc/design/syn/S12.html says:
You can also mixin a precomposed set of roles:
$fido does Sentry | Tricks | TailChasing | Scratch;
Should that be the following?
$fido does Sentry & Tricks & TailChasing & Scratch;
Cheers,
Ovid
--
Buy the book -- http://w
ork, instances of objects in the M, V, or C portions
might want to exhibit different behaviors, depending upon what I'm
doing with them, but I don't necessarily want those behaviors to bleed
over to the other layers of my application. Whether or not this is a
clean way of looking at the p
ll (see Moose::Meta::Class for more about these
> APIs):
>
> ^Dog.add_role(^Catlike);
That's more of what I was thinking, but where is this documented? I
can't find it in http://dev.perl.org/perl6/doc/design/syn/S12.html. I
see it in the Moose docs, but is this in Perl 6? I
nge. Can anyone else reproduce
this? If not, I can dig into my system and see what's up.
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
--- Gaal Yahas <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 12, 2006 at 02:14:42AM -0800, Ovid wrote:
> > pugs $ pugs t/general/basic.t
> > pugs: user error (***
> > Unexpected "Str"
> > expecting "\\", ":", "*&qu
, it's flattening nested lists
and I'm embarrassed to admit that I can't figure this out in Perl6.
Thoughts? I've been reading synopses and grepping through Pugs, but to
no avail.
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
ugs line 103, column 13-22
Take out the returns, and it works fine. Can someone tell me what I'm
missing? Is this a bug.
Also, I noticed I accidentally left off the final semi-colon on the do
block. It ran anyway and that surprised me.
Cleaner ways of writing that code are welcome, too.
would like.
The link to my sample Perl6 code and to the original 99 problems is at
http://perlmonks.org/?node_id=590113
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
ot;, [1, "c"] ).perl.say;
Oddly, using the postfix ++ gives me the error message I expect:
*** Can't modify constant item: VRef
at 99.pugs line 215, column 18-69
99.pugs line 215, column 18-69
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
omething break? If so, I'll add a
test. Otherwise, what's wrong with this code? Also, I've been
searching the docs for the exact syntax of 'gather/take' and I can't
find it. Pointers would be great.
Pugs Version: 6.2.13 (r14911)
Cheers,
Ovid
--
Buy the book -- http://w
omething break? If so, I'll add a
test. Otherwise, what's wrong with this code? Also, I've been
searching the docs for the exact syntax of 'gather/take' and I can't
find it. Pointers would be great.
Pugs Version: 6.2.13 (r14911)
Cheers,
Ovid
--
Buy the book -- http://w
,), (3,), (4,), (5,), (6,), (7,), (8,), (9,), (10,))
>
> /s
It looks like there's a bug in gather/take and luqui is working on it
now (from #perl6).
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
27;ll happily commit tests, but what is the expected behavior of my
first code snippet?
(I see now that other junction tests use ok() instead)
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
1 - 100 of 349 matches
Mail list logo
