Re: Pod::Critic?

On 6/6/07, Ian Malpass <[EMAIL PROTECTED]> wrote: I've been documenting lately, so I'm a bit POD-focussed at the moment :) I was pondering creating Pod::Critic, as a documentation analogue of Perl::Critic. Clearly it's not so easy to give hard-and-fast rules about documentation, but I thought it

Re: YAML?

On 3/19/07, Mark Fowler <[EMAIL PROTECTED]> wrote: On 19 Mar 2007, at 13:03, Adrian Howard wrote: > Nope. It's to add some simple YAML-ish output in places to help > clarify things. It's also a very small subset of YAML rather than > the full YAML spec. > See

Re: What the 'runtests' output looks like

On 1/15/07, Ovid <[EMAIL PROTECTED]> wrote: Hi all, If you've not checked out TAPx::Parser lately, here's what the 'runtests' output looks like: http://publius-ovidius.livejournal.com/222624.html it's nice to see color output (too bad it won't work on windows--cmd.exe's problem, not yours.)

Re: TAPx::Parser 0.05_03

On 1/8/07, Ovid <[EMAIL PROTECTED]> wrote: It's on its way to the CPAN now. Thanks for lots of feedback. I'd really love to hear from Windows users as to whether or not it seems to work OK there. 28 regression tests are failing, otherwise, all tests are passing. t/010-regression.t 28 7168

Re: Comment about BAIL_OUT

On 1/4/07, Andy Lester <[EMAIL PROTECTED]> wrote: On Jan 4, 2007, at 11:21 PM, Eric Wilhelm wrote: >> No. You either have tests that are ordered, or you don't. > > Stated as if it were some sort of immutable law of the universe! It is as far as Test::Harness goes. Test::Harness doesn't have

Re: TAP 2.0

On 9/29/06, Ovid <[EMAIL PROTECTED]> wrote: got: this is line 1 this is line 2 this is line 3 expected: this is line 1 this is line b this is line 3 i prefer this syntax, as it's easier to parse in languages without builtin he

Re: Time to pack

On 9/28/06, Ovid <[EMAIL PROTECTED]> wrote: Can someone tell me why this test fails? your pack template is one item long. try C<'u*'> instead. ~jerry

TAP parsing and standard errors -- changing the problem (was Re: Merging STDOUT and STDERR)

it is obvious that, in the general case, managing multiple streams on multiple filehandles using existing technologies is a *hard* problem. it does, however (and thanks for the hint barrie) seem possible to solve the problem for special cases--those you can control. On 9/22/06, Barrie Slaymaker <

Re: Merging STDOUT and STDERR

On 9/21/06, Ovid <[EMAIL PROTECTED]> wrote: OK, I'm stuck. I've read through IPC::Open3 and friends, I've looked through CPANPLUS, I've tried to solve this problem but no matter how hard I try, while I can fetch both STDOUT and STDERR, I cannot guarantee that they're in synch. That's my big

Re: New TAP Grammar

On 9/14/06, Ovid <[EMAIL PROTECTED]> wrote: - Original Message From: jerry gay <[EMAIL PROTECTED]> > thanks for the responses. i've done a second take on the TAP grammar > in perl6 format, with the help of patrick michaud. i'm pretty sure > it'

Re: New TAP Grammar

thanks for the responses. i've done a second take on the TAP grammar in perl6 format, with the help of patrick michaud. i'm pretty sure it's correct now, at least as per your previous grammar. have a look: grammar TAP; ## Ovid's TAP grammar, translated, corrected, and rendered idiomatic ## NOTE:

Re: New TAP Grammar

On 9/14/06, Ovid <[EMAIL PROTECTED]> wrote: I'm not particularly gifted with grammars, so corrections welcome. The corrected TAP grammar: digit ::= [:digit:] character ::= ([:print:] - "\n") positiveInteger::= ( digit - '0' ) {digit} nonNegativeInteger ::= digit {d

Re: post-YAPC::Europe CPANTS news

On 9/6/06, chromatic <[EMAIL PROTECTED]> wrote: On Wednesday 06 September 2006 02:53, Thomas Klausner wrote: > - buildtool_not_executable > Check if the buildtool (Makefile.PL, Build.PL) are not executable > (and thus need to be called with 'perl Build.PL' thereby specifying > which exact versio

soliciting TAP comments from language designers (where to begin?)

as i work on parrot, i happen to know a few language designers. i know they're interested in providing feedback on the proposed TAP changes, but (perhaps because i'm new to the list) i don't see a good thread to point them to. is there a summary of changes, or something i've missed that would be a

Re: designing a test suite for multiple implementations (tools thread)

On 8/14/06, chromatic <[EMAIL PROTECTED]> wrote: Ugh, so this means editing the canonical test repository for every status-changing update to every implementation? Yuck. This seems like a problem for implementation-specific harnesses and reporting tools. this is what prompted me to start th

Re: designing a test suite for multiple implementations (tools thread)

[parrot-porters and p6l have been removed from this thread, as discussion of testing tools is not directly related to those lists] On 8/11/06, Agent Zhang <[EMAIL PROTECTED]> wrote: On 8/12/06, jerry gay <[EMAIL PROTECTED]> wrote: this last testing rule i mentioned beco

Re: designing a test suite for multiple implementations

On 8/11/06, Larry Wall <[EMAIL PROTECTED]> wrote: Just to avoid repeating some of the discussion, here's a link to #perl6: http://colabti.de/irclogger/irclogger_log/perl6?date=2006-08-07,Mon&sel=110#l193 The discussion goes on and off for most of the rest of the page, so you probably want

designing a test suite for multiple implementations

recently, perl 6 development has taken the form of a multi-method dispatch. that is, multiple implementations are under active development. this includes pugs (in haskell,) v6 (in perl5,) v6-Compiler (in perl6,) and perl6 (on parrot.) hopefully, each of these returns the same result, a working[1]

Re: TAPx::Parser 0.10 (now with stream support)

On 7/24/06, Ovid <[EMAIL PROTECTED]> wrote: http://users.easystreet.com/ovid/downloads/TAPx-Parser-0.10.tar.gz Not having a 'net connection in my flat yet meant that I was mostly flying blind and had to try and recall what was said on the list from memory. As a result, I'm sure that what I've

Re: TAP diagnostic syntax proposal

On 7/13/06, Jonathan Rockway <[EMAIL PROTECTED]> wrote: > are you serious? listen to what they people here are saying - we _all_ > read the raw TAP output, all the time, and not because we're TAP > developers interested in the underlying implementations. as users, the > (current) raw TAP diagn

Re: TAP diagnostic syntax proposal

On 7/11/06, Jonathan T. Rockway <[EMAIL PROTECTED]> wrote: Ian Langworth wrote: > I mentioned YAML with a pretense I failed to mention -- that we > wouldn't parse the YAML. That's already been done, and there are > plenty of parsers. I agree with this. YAML has been done and done again, in ev

new! parrot tap parser

at the chicago hackathon, i decided to create a simple tap grammar using perl 6 regexes. you can find the example grammar at: http://svn.perl.org/parrot/trunk/examples/pge/grammars/TAP.pg that spawned interest from chris dolan on creating a parser using parrot's parser grammar engine (pge.) to

Re: TAP Grammar

, etc.) into my brain, so any >> additional >> examples would helpful, interesting, and fun. For me, anyway :) > > Jerry Gay just wrote a PGE TAP grammar: > > <http://svn.perl.org/parrot/trunk/examples/pge/grammars/TAP.pg> > > -- c I hacked a rudimentary t