Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Test::Harness's TAP in C -- libtap More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

comments on plan... (Score:1)

by rooneg (3732)

Why have three separate plan functions?
I would have thought you'd just do a single 'plan' function, which takes an integer as its first arg and then varargs after that.
Define constants like NO_PLAN and SKIP_ALL as negative numbers, a positive number for the first arg corresponds to the current plan_tests, NO_PLAN as the first arg corresponds to plan_no_plan, SKIP_ALL corresponds to plan_skip_all, and you grab the string from the varargs to get the equivalent of the current plan_skip_all's argument.
- Re:comments on plan... (Score:1)
  
  by nik (3476)
  
  Why have three separate plan functions?
  
  Rough consensus on #london.pm -- originally the code did much as you suggest (although it looks like I didn't commit that, there's a hangover from it in one of the test files [ngo.org.uk]).
  - Re:comments on plan... (Score:1)
    
    by rooneg (3732) on 2004.12.05 13:49 (#36547) Journal
    
    Interesting. I like the old way much better, the multiple different plan functions seems like it makes the C version different from the perl version when there's no good reason to do so.
    
    Reply to This
    
    Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.