in reply to Re: Re: Re: Module Creation
in thread Module Creation

My worry is that the "boring crap" very often ends up being either "important crap" or "useless-gets-in-the-way crap". If a module that was solely for internal use and now needs to be distributed in a CPAN-like way, take the time to learn why the MANIFEST (for example) is desirable. The second and subsequent times, use h2xs, by all means.

I guess I'm old-fashioned. I feel that people should know at least the basics of the tools they're using. *shrugs*

Replies are listed 'Best First'.
Re:+ Module Creation
by TGI (Parson) on Jul 17, 2001 at 22:45 UTC

    Good point--makes me think of my calculus teacher that required that we prove that the derivative shortcuts in our text were valid before we could use them. However having a nice clean distro skeleton to look at can be a real asset when your are studying the anatomy of modules.

    My philosophy is to avoid autogenerated code that I don't understand. But I've learned a lot in various enviroments by disecting autogenerated code.


    TGI says moo

[reply]

In Section Seekers of Perl Wisdom