On Fri, Mar 27, 2015 at 8:35 AM, Tom Browder <tom.brow...@gmail.com> wrote: > Use a separate module (but included with the code for the whole > package) for the non-class-specific, formerly-private methods to be > "public", .... because some of the private > methods are really general math subroutines. That way I can test > those subroutines without breaking OOP (I think).
That's a double win, both making the larger module better organized and creating a new module of general utility. > the use statement for the modules would be inside the > class-specific methods that need them (a new, restricted scoping in > Perl 6 I understand). Hmm, I never thought about the scoping of "use" in Perl 5, but that makes sense- exports in Perl 5 are into the namespace of the current package, not lexical- though a package declaration is lexical. Learn something new every day.... -y
