On Jun 22, 2012, at 1:01 PM, Matt S Trout <m...@shadowcat.co.uk> wrote:
> On Fri, Jun 22, 2012 at 12:49:25PM -0500, brian d foy wrote: >> [[ This message was both posted and mailed: see >> the "To," "Cc," and "Newsgroups" headers for details. ]] >> >> In article >> <CALRLLbDrr9=upzga7k35czkdqgg22pm9he3dzva6qdqw+-p...@mail.gmail.com>, >> Adam <a...@spatialsystems.org> wrote: >> >>> I need to split files by size, but they have to be split only on newlines. >>> So the size can be close, but it has to be split in the right spot. >>> >>> I propose using the name File::Split::More, File::Split::Qualifier, or >>> File::Split::ApproxSize. I posted the details here: >> >> I think a more appropriate name would be something like >> File::Split::Boundary or File::Split::Aligned. The size is a side >> effect, not the functionality. :) > > File::Split::BoundaryAware or File::Split::OnBoundary would've been my > thoughts. > > However, that's just details; I agree entirely with Brian's breakdown of > which is the functionality and which is incidental. > > -- > Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a > clue > > http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ > > Email me now on mst (at) shadowcat.co.uk and let's chat about how our Catalyst > commercial support, training and consultancy packages could help your team. Someone suggested that I take over File::Split since it has had a bug report for 6 years and it fails all tests on the cpan testers framework. The POD also says the interface may change. Should I change the interface and add my features?
