Alex Becker
2014-10-08 17:59:12 UTC
Hi!
When creating the base for a new CPAN module using h2xs (e.g. with the
command h2xs -b 5.10 -XA -n Super::Duper::Module), there is a lib folder
created.
In this lib folder, the name space is mirrored by a directory tree (e.g.
lib/Super/Duper/Module.ppm).
Now, while browsing CPAN, I noticed some older modules not having a lib
folder.
So, I personally like the lib folder because it's easy to identify where
the module's code resides.
But, is there any other advantage? Or to ask in another fashion: is it
recommended to use a lib folder and if yes, why?
Kind regards,
Alex
When creating the base for a new CPAN module using h2xs (e.g. with the
command h2xs -b 5.10 -XA -n Super::Duper::Module), there is a lib folder
created.
In this lib folder, the name space is mirrored by a directory tree (e.g.
lib/Super/Duper/Module.ppm).
Now, while browsing CPAN, I noticed some older modules not having a lib
folder.
So, I personally like the lib folder because it's easy to identify where
the module's code resides.
But, is there any other advantage? Or to ask in another fashion: is it
recommended to use a lib folder and if yes, why?
Kind regards,
Alex