-----BEGIN PGP SIGNED MESSAGE-----
On Tuesday 15 June 2010, Kirk H. [email protected] wrote:
The best practice is to put it where it makes sense to put it, bearing
in mind you might have to read your code again in two years, or
someone else might have to read your code.
If you move your requires, I’d put them outside of the class bodies
and method bodies, but as close to the relevant code as is reasonable.
thanks for your answer. I’ve been digging into the RDBI sources to
my curiosity and found it the way you described.
The RDBI sources brought up another question for me, which I append here
because it seems loosely related.
Consider this code:
class Foo::B < Foo::A
First question: Is Foo::B part of the “Foo” module and the Foo
The latter I guess it’s true, but with the first one I’m not sure and I
no idea how to check.
Plus, what difference does it make for a class to reside within a module
outside? I know that modules are useful as mixins, which also means one
defines a set of methods without them beloning to a particular class.
for a complete class to be part of a module, does that make sense? I.e.,
one mixin a class into another?
Thanks alot in advance for any insight.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----