Re: Namespace advice for Git-related package

James E Keenan writes: > I am in the process of developing a CPAN library which I am > considering calling Git-Multisect-Perl. ... > > 'Multisect::' is chosen to contrast with 'bisect'. That hadn't occurred to me. I read it as a contraction of ‘multiple sections’ or similar. > When we speak of

Re: PDLx::Mask - search.cpan.org uses README.pod instead of lib/PDLx/Mask.pm

Thanks. I'll move the README.pod somewhere innocuous. On Wed, Oct 26, 2016 at 6:52 PM, Dan Book wrote: > On Wed, Oct 26, 2016 at 6:14 PM, Diab Jerius > wrote: >> >> Howdy, >> >> The PDLx-Mask distribution has a README.pod file at the top level, as >>

Re: How to avoid circular module dependencies within a distribution?

David Christensen: > Here is a contrived example that shows circular modular dependency > without circular subroutine dependency: In this particular case, I'd move subs bar2 and foo2 to another module FooBar.pm, and have Foo.pm and Bar.pm import those subs from FooBar.pm instead: > 2016-10-19

Re: Sanity checking for namespace and other abuses

* David Mertens [2016-10-26 18:12]: > Does anybody oppose me adding to code to top-level, lower-cased > packages "int", "num", and "str"? What about top-level packages "Int", > "UInt", "Str", or "Num"? Do other type systems use these top-level > packages? Yes. You would