Looking at Synopsis 12, I notice that the "Enums" section refers to a
"str" type, but Synopsis 6 doesn't, so there is an inconsistency here
that needs correcting.
At first I thought S12 could be updated to use "Str" instead, but
then when looking closer it seemed to me that the enum seemed to
On Tue, Jun 27, 2006 at 09:04:27PM -0700, Dave Whipp wrote:
> I was reading the slides from PM's YAPC::NA, and a thought drifted into
> my mind (more of a gentle alarm, actually). One of the examples struck me:
>
> rule parameter_list { [ , ]* }
>
> Its seems common in the higher layers of a g
As Test::Expect was just mentioned here, I would like to know why Expect and
thus Test::Expect does NOT work on Windows?
I have also asked this on use.perl:
http://use.perl.org/~gabor/journal/30069
Gabor
I was reading the slides from PM's YAPC::NA, and a thought drifted into
my mind (more of a gentle alarm, actually). One of the examples struck me:
rule parameter_list { [ , ]* }
Its seems common in the higher layers of a grammar that there are more
non-terminal than terminals in each rule, so
From: Steffen Schwigon [mailto:[EMAIL PROTECTED]
> Thomas Wittek <[EMAIL PROTECTED]> writes:
> > Maybe we should steal the ruby "principle of least surprise" here,
> > which I find a very good principle.
>
> I'm quite confident that Larry already stole all good principles he
> could find.
Me too
在 2006/6/27 下午 4:41 時，Patrick R. Michaud 寫到：
For any who may be interested, my talk slides for
"Perl 6 Compiler Status and the Parrot Compiler Toolkit"
(presented today at YAPC::NA) are available at
http://www.pmichaud.com/2006/pres/yapc-perl6/slide.html
That was a wonderful talk. Thank
For any who may be interested, my talk slides for
"Perl 6 Compiler Status and the Parrot Compiler Toolkit"
(presented today at YAPC::NA) are available at
http://www.pmichaud.com/2006/pres/yapc-perl6/slide.html
The slides for my second talk "Parser, Perl 6 Rules, and
the Parrot Grammar Engine
On 27 Jun 2006 15:01:43 -, Rafael Garcia-Suarez
> my $CLASS;
> BEGIN {
> $CLASS = 'Some::Module';
> use_ok $CLASS or die; # "or die" saves the day
maybe BAIL_OUT could be better than die here, in at least a few cases.
It depends on if you want to stop just this test script
# New Ticket Created by Will Coleda
# Please include the string: [perl #39648]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39648 >
'lastpos' is a bad variable name, and should be changed. - Patrick
(regarding PGE-gener
Ovid wrote in perl.qa :
>
> You've run into a problem which surprises a few folks but definitely
> causes problems. In a nutshell, use_ok internally traps the "use"
> call with an eval. However, even if it fails (as in your case), the
> bytecode might still be compiled and in memory and, as a res
- Original Message
From: Geoffrey Young <[EMAIL PROTECTED]>
> so, the compile test failed, but bar() could still be called and, in
> fact, even executed successfully.
Hi Geoff,
You've run into a problem which surprises a few folks but definitely causes
problems. In a nutshell, use_ok
hi all :)
so, as a standard practice, I start with
use_ok($class);
as the first test in each file, the idea being that if the class doesn't
compile I shouldn't care about the results of the rest of the test - I
know immediately that subsequent failures are because I introduced a
typo or someth
On 6/25/06, Ian Langworth <[EMAIL PROTECTED]> wrote:
Looks a little familiar.. Great job!
I first wrote it about 2 years ago but only recently decide to
make it available to the general public.
I decided to do so now so it won't come out after the
Big Perl Testing Book you mentioned in here:
ht
On 6/26/06, Leon Brocard <[EMAIL PROTECTED]> wrote:
This is really neat. You might want to add a link to Test::Expect too,
which makes it almost to easy to test terminal-based programs.
I only recently saw Test::Expect, I'll look at it more deeply and
will include a set of examples using it as
HaloO,
Paul Hodges wrote:
so back to foo("bar"). What's the default behavior? String doesn't Num,
does it? though is does convert if the value is good
I think that Str and Num are disjoint mutually exclusive types.
If you want to get coercive behaviour you need an overloaded
&foo:(Str|Num
15 matches
Mail list logo
