James E Keenan said:
I learned a tremendous amount about testing, code coverage and
writing testable code from the Phalanx project -- knowledge which
has served me well, particularly in the Parrot project. The
approach to 'phalanx'-ing a module can be applied by anyone (and I'm
happy to mentor people on that).
Would you be interested in putting your experiences into a "Howto"
form? (preferrably as terse as possible)
I think the Phalanx project is still useful as a concept and as a
"teaching tool" and if we should repurpose the Phalanx page into
something more useful than the "mission statement/overview" type page
we have now, then this would be it. :)
But, to the best of my knowledge, there's no active Phalanx project
per se at the present time. So it doesn't need to be quite so
prominent on qa.perl.org.
I'd instead decide prominence on the _intention_ of activity, not the
current state or the history of the project. What do we WANT to do is
more important than what has been done (the point here is to convey
the fact that the Perl QA has a future, and that it's more important
than what has been done.)
- Salve
--
#!/usr/bin/perl
sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print# Salve Joshua Nilsen
getc DATA}$"="'};&{'";@_=unpack("C*",unpack("u*",':4@,$'.# <[email protected]>
'2!--"5-(50P%$PL,!0X354UC-PP%/0\`'."\n"));eval "&{'@_'}"; __END__ is near! :)
