On Monday, Dec 2, 2002, at 14:34 US/Pacific, james lundeen wrote:
[..]
i too need to know exactly how to do this. anyone
out there that can help us, it would be much appreciated! -jim
--- Will <[EMAIL PROTECTED]> wrote:
[..]
My questions have been - 1.) "How do I create the
library?", and 2.) "How do I use the library?"
[..]
I should first start by saying I am an 'h2xs' "bigot"
and religiously believe in starting any new perl module,
especially 'pure perl modules' with
h2xs -AX -n FOO::BAR
my General ranting on this is at:
http://www.wetware.com/drieux/CS/lang/Perl/PM/
If you follow the 'just show me a case study' to
http://www.wetware.com/drieux/CS/Proj/PID/
I try to walk through the basic process of starting out
with a silly Idea and creating a perl module.
The Other 'hot button' topic of course is whether or not one
should 'use lib' or require using the PERL5LIB environmental
variable... I once had an opinion, I have since violated all of them.
cf: http://www.wetware.com/drieux/CS/lang/Perl/PM/useLibHack.html
Somewhere in all of this you will run into the usual problems
about whether or not you should make it 'oo' or should resolve
the name-space-management issues. Good Luck, there are opinions.
May I recommend that the principle advantage of starting with
the h2xs approach, in the *nix environment, is that one can build
a CPAN style approach that can EITHER be installed where ever it
is that the perl built for that host knows where site_perl resides,
or you can over-ride that with installing it into your home directory,
or the 3rd path of installing them into 'other places' such as
/usr/local/lib/MyProjectHere
so that everyone has to have that in the @INC by what ever means.
HTH.
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
