# New Ticket Created by Ramesh Srinivasan
# Please include the string: [perl #39688]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39688 >
Hi,
When ever I execute the following module I get the error. Kindly help us to
"Michael G Schwern" wrote in perl.qa :
> * What about Test::Harness?
>
> Test::Harness remains its own thing.
>
> At some point in the future Test::Harness will likely be gutted and
> turned into a thin wrapper around TAP::Harness. I'm not caring about
> this right now.
What about prove(1) ? Are
On 02/07/06, Adam Kennedy <[EMAIL PROTECTED]> wrote:
Fergal Daly wrote:
> On 02/07/06, Adam Kennedy <[EMAIL PROTECTED]> wrote:
>> > There's no way to declare a top-level plan. That is, I can't say how
>> > many groups of tests I'm going to run so there's effectively no plan,
>>
>> One point that
On Sunday 02 July 2006 23:37, Adam Kennedy wrote:
> > The most up-to-date Test-Run code is here:
> >
> > http://svn.berlios.de/svnroot/repos/web-cpan/Test-Harness-NG/
> >
> > I don't mind giving Subversion access to the repository to anyone who
> > registers in http://developer.berlios.de/ and is e
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
follow
On Jul 2, 2006, at 11:23 PM, Uri Guttman wrote:
hi to all docathon hackers (and others too),
one idea we came up with during the docathon is that perl6 needs a
glossary. would the terms autobox or mixin make any sense to a newcomer
who didn't know any OO theory? so this is a proposal to start
That seems like a problem too but the one I'm trying to get at is
4 no plan, with groups
If your script exits prematurely after one of the groups, the harness
will not notice because everything looks just fine. The solution to
this is not to use "plan, with groups" because then you have to coun
On 3 Jul 2006, at 13:56, Adam Kennedy wrote:
That seems like a problem too but the one I'm trying to get at is
4 no plan, with groups
If your script exits prematurely after one of the groups, the
harness
will not notice because everything looks just fine. The solution to
this is not to use
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Jul 3 13:15:01 2006 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with mo
If we don't have some way of signifying the end of a group in TAP then
it removes a chunk of the utility for the people writing things that
generate TAP - since everybody has to write their own checks that groups
actually output the number of tests that they should.
If we have an end-of-group
On Jul 3, 2006, at 4:29 AM, Rafael Garcia-Suarez wrote:
What about prove(1) ? Are you going to make a version of it that uses
TAP::Harness ? And it so, will it be removed it from T::H ? (I hope
not,
since it's part of the core). Or have a fork ?
No, prove will be in both Test::Harness and
On 03/07/06, Adam Kennedy <[EMAIL PROTECTED]> wrote:
> That seems like a problem too but the one I'm trying to get at is
>
> 4 no plan, with groups
>
> If your script exits prematurely after one of the groups, the harness
> will not notice because everything looks just fine. The solution to
> th
On 7/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
+But parens are special that way. (Even C is assumed to be a
+function call rather than a quote.) Other bracketing characters are
+special only if they can be mistaken for adverbial arguments, so
qn[stuff]
-is fine, while
+is fine,
Hi!
This is a small Request For Feedback.
I want to hear if *anyone* who writes or experiments with Perl6/Pugs
these days uses (X)Emacs to write his/her code. If so, would you
please try out the enhanced cperl-mode from
http://svn.openfoundry.org/pugs/util/cperl-mode.el
Some additional help fo
All:
I have a for-fun project that I am working on exploring various different
parsers and their methods. So far I have looked at things like
Parse::RecDescent, Parse::YAPP, Parse::Earley, and HOP::Parser. I had
Perl6::Rules on my list, but it is my understanding that
Pugs::Compiler::Rule is mor
On Mon, Jul 03, 2006 at 05:31:34PM +0300, Markus Laire wrote:
: On 7/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
: >+But parens are special that way. (Even C is assumed to be a
: >+function call rather than a quote.) Other bracketing characters are
: >+special only if they can be mistaken
2006/7/3, Joshua Gatcomb <[EMAIL PROTECTED]>:
I am specifically interested in examples that can be run in Perl 5 today
without needing Pugs or Parrot.
http://svn.openfoundry.org/pugs/perl5/Pugs-Compiler-Rule/compile_p6grammar.pl
- doesn't do exactly what you want, but you can see what the synt
- Original Message
From: Jonathan T. Rockway <[EMAIL PROTECTED]>
> I would say that even if nobody else is interested, if you're
> interested, do it :)
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 gramm
- Original Message
From: Michael G Schwern <[EMAIL PROTECTED]>
> 1. I want to name a group of tests rather than the individuals.
...
> Here's what we came up with.
>
> 1..10
> ..4 - name for this group
> ok 1
...
> Pros:
> * Its backwards compatible. The ..# lines are currently considere
This ended up in the queue for parrot (perl 6 vm) problems, not the perl5 queue.
Changing queues.
On 3 Jul 2006, at 17:47, Ovid wrote:
- Original Message
From: Michael G Schwern <[EMAIL PROTECTED]>
* Its backwards compatible. The ..# lines are currently considered
junk and ignored.
Is this behavior documented anywhere?
[snip]
From Test::Harness::TAP
Anything else
Any output
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
> produce some output which doesn't make sense.
Isn't this the syntactic/semantic problem common to all
Hi
It would be nice if the documents at http://www.parrotcode.org/docs/
were equipped with last modification date.
/Rene
On Jul 3, 2006, at 5:52 AM, Ovid wrote:
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?
No no no, please do. I will be glad to put it in TAP
- 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
> > produce some output which d
Author: larry
Date: Mon Jul 3 12:00:53 2006
New Revision: 9753
Modified:
doc/trunk/design/syn/S04.pod
Log:
Clarifications on stack unwinding semantics of exception handlers.
Modified: doc/trunk/design/syn/S04.pod
==
On Monday 03 July 2006 11:43, Steve Peters via RT wrote:
(from p5p)
> OK, with change #28473, I just added the capabilities to a stat() or -X
> filetests for systems with the dirfd() libc call available. There are
> two additional steps that need to be done. First, Perl_pp_stat and
> Perl_my_st
Will Coleda wrote:
> While you're waiting, we should improve the test for readline: we
> used to have similar failures where we found readline (or other
> probed thingees) but the version was not recent enough for us to link
> with.
(1) Some sort of grouping for the libraries so that only th
Thanks muchly for this contribution. I love making failing tests pass.
There are some adjustments needed, though, before we can integrate this
patch into Parrot.
The use of a fixed constant like MAX_REGISTER doesn't really work; Parrot
has an unbounded (if not infinite :-)) number of registers, s
On 7/3/06, Ovid <[EMAIL PROTECTED]> wrote:
Currently, the way that Test::Harness::TAP reads, I should properly discard
anything which is not a plan, test or diagnostic output. However, test failure
output and programmer supplied diagnostic output need to be disambiguated or
diagnostic informa
# New Ticket Created by Vishal Soni
# Please include the string: [perl #39694]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39694 >
On Mon, 2006-07-03 at 13:03 -0700, Chip Salzenberg wrote:
> Thanks muchly for this contr
On Mon, 2006-07-03 at 13:03 -0700, Chip Salzenberg wrote:
> Thanks muchly for this contribution. I love making failing tests pass.
> There are some adjustments needed, though, before we can integrate this
> patch into Parrot.
>
> The use of a fixed constant like MAX_REGISTER doesn't really work;
- Original Message
From: Michael G Schwern <[EMAIL PROTECTED]>
> Diagnostic information *is* unreliable in TAP.
> Do not parse it.
It is now being discarded.
> Test::Harness does not allow a leading space. There's no reason to start.
OK. Thanks.
> Test::Harness handles directives ca
On Mon, Jul 03, 2006 at 03:39:19PM -0500, Vishal Soni wrote:
> On Mon, 2006-07-03 at 13:03 -0700, Chip Salzenberg wrote:
> > The use of a fixed constant like MAX_REGISTER doesn't really work; Parrot
> > has an unbounded (if not infinite :-)) number of registers [...]
> > You'll have to use the INTV
On Mon, Jul 03, 2006 at 12:22:15PM -0700, chromatic wrote:
> On Monday 03 July 2006 11:43, Steve Peters via RT wrote:
>
> (from p5p)
>
> > OK, with change #28473, I just added the capabilities to a stat() or -X
> > filetests for systems with the dirfd() libc call available. There are
> > two add
Hello.
If no one has a problem with it, I'd like to volunteer to be pumpking
for this doc. I saw juerd on perl6-lang mentioned
http://pugs.kwiki.org/?Perl6Nomenclature as a possible starting point,
but Uri's description calls for something a bit more descriptive.
Joel York [Shadowhawk]
-Orig
> In any case, I was wondering if someone could provide me with an example of
> a mathematical expression parser (and evaluator).
> To properly compare to the others, it would need to handle the following
> operators
>
> +, - (left associative)
> *, /, % (left associative)
> ^ (right as
# New Ticket Created by Chip Salzenberg
# Please include the string: [perl #39695]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39695 >
On Mon, Jul 03, 2006 at 03:39:19PM -0500, Vishal Soni wrote:
> On Mon, 2006-07-03 at
On Monday 03 July 2006 09:01, Jonathan T. Rockway wrote:
> That said, I would be interested. I'm still trying to page all the
> perl6/parrot grammars (PGE, TGE, etc.) into my brain, so any additional
> examples would helpful, interesting, and fun. For me, anyway :)
Jerry Gay just wrote a PGE TA
# New Ticket Created by Chip Salzenberg
# Please include the string: [perl #39693]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39693 >
Thanks muchly for this contribution. I love making failing tests pass.
There are so
Patrick R. Michaud wrote:
you change to
$P99 = get_namespace key_or_array
$P0 = $P99['foo']
which also incidentally encourages(!) compilers to cache namespace pointers.
Ooh. I like it very much!
Okay, to flesh this out as a viable alternative, Chip/Patrick we need:
a) a standard
I would say that even if nobody else is interested, if you're
interested, do it :)
That said, I would be interested. I'm still trying to page all the
perl6/parrot grammars (PGE, TGE, etc.) into my brain, so any additional
examples would helpful, interesting, and fun. For me, anyway :)
Rega
# New Ticket Created by Will Coleda
# Please include the string: [perl #39696]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39696 >
Currently the perl6 makefile is in the root parrot config dir: config/
gen/makefiles/pe
On Mon, Jul 03, 2006 at 07:37:00PM -0700, Will Coleda wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #39696]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=39696 >
>
>
> Currently the
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39697]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39697 >
Tcl comes with several procedures that are actually written in Tcl as
part of the s
Changes for 6.2.12 (r10930) - June 26, 2006
Licensing Changes
The src/ tree and the
pugs
executable are now released under the permissive MIT license, in addition to Artistic and GPL
A new third-party/ tree to hold bundled prerequisites originated from non-Pugs projects
New Perl 6 modu
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39698]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39698 >
[expr]'s current implementation is less than optimal in terms of
developer time. It
Finally, the moment you've all been waiting for is here!
perlbug (http://rt.perl.org/rt3/) has been upgraded to the latest and
greatest version (RT 3.6).
Here are some changes you might notice:
- a new shiny look
- no more auth.perl.org, we now authenticate directly from bitcard.org
- a p
48 matches
Mail list logo
