On Sunday, June 23, 2002, at 10:11 , Timothy Johnson wrote:
[..]
> If you put the module above in a file called UC.pm in the site/lib/Tim
> folder, you will have a module with your reusable subroutine. The only
> weird part: Don't forget that the last line should be just a '1'. Just
> put
> a use Tim::UC; at the top of your script and you're set. I keep mine in
> the
> Tim tree so I won't bump into any future CPAN modules, but you can easily
> see how to use this for your particular situation.
[..]
funny you should say that!!!
I actually use two different name spaces I use:
Wetware::ThisModule
dtkp::ThatModule
the former are things that I do and blame on the
myFascistOverLord of wetware.com - the later comes
from the whole
drieuxishToolKit(Play|Perl|Pomposity|PromiscuousKodingKadaver|PhraseHere)
sequence of code games...
The reason that i keep 'preaching' this Idea of use h2xs
and for the Purely Perl Modules - "h2xs -AX" will work
way too wicked slick - until you feel at home about whether
your design pattern supports 'autoloaders' - is that this
way you get all the cool widgets for free...
all the frame work just you ever wanted, including the
@EXPORT_OK....
POD section
The Makefile.PL
Change file
the makefile already knows to check the t/*.t subdirectory
for alternative tests - and that is where you can localize
your code development for a module - and of course if
you have stuff already - ..... if you upgrade... you upgrade
your tests....
You have the basic CPAN style approach - and can gin up the tarball -
make dist
hang it in your URL's and let folks grab them...
If they like it they can run
make install
and it will autoMajikally hang it in the required site_perl
location on their machine....
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
