Why this module as the next "porting a module"
1. Genuinely useful (for many things)
2. Very heavily tested, with tests accumulated for corner cases and
weirdities
3. No non-core dependencies
4. Not too big, not too small
But really, autrijus just wants an implementation of Test::Inline 2.00
at the same time as it ends up in CPAN for P5.
=begin testing method after othermethod Needed::Class 25
... the 25 tests for method 'method'
=end testing
It handles method and class-level ordering and will do entire trees of
code in one pass.
Any response, please also CC as I'm not on the list. Thanks
Adam K
Wonderful, you++! :)
Thanks,
/Autrijus/
As a reminder to those of you for whom it isn't common sense, the
standard way to distribute code on the internet involves having all
of your files encoded using UNIX line-breaks (not DOS/Windows, not
MAC OS 9).
All of the Algorithm::Dependency files had DOS linebreaks, and my
first commit of them mainly involved changing them to UNIX
linebreaks. They should have been UNIX at the initial checkin of the
Perl 5 code.
I made very few other changes in this commit (just #! and etc), and I
made them prior to discovering the linebreak problems. Since any
further changes will be a separate commit, it will be easier to see
what changes were made between versions.
-- Darren Duncan
Actually, as we are using Subversion, there is a good way to solve this:
svn ps -R svn:mime-type "text/plain; charset=UTF-8" modules
svn ps -R svn:eol-style native modules
This way, everyone will be able to checkout the files with the
local encoding. I have previously done so for lib/, t/, src/ and ext/,
and I've just committed a change that sets them to modules/ too. :)
Thanks,
/Autrijus/
Thanks.
Adam