Re: If it is not a core module, then what is it?

I usually use the terms core and standard module interchangeably to indicate that they come with the version of Perl I have. I use CPAN or non-standard modules to mean other modules you can get from CPAN. I don't usually say non-core. I don't normally use modules outside of those categories unless someone in my shop wrote them.

I don't like the term third party, since I'm not quite sure what it means. I prefer to make the distinction this way. There are standard modules that come with Perl, CPAN modules for common problems, in house code for our particulars, and out house code for things given to us by vendors.

Phil

Comment on Re: If it is not a core module, then what is it?

Replies are listed 'Best First'.
Re^2: If it is not a core module, then what is it? by bibliophile (Prior) on Sep 29, 2006 at 14:14 UTC
Heh. "out house code" - does that refer to where it was developed, or the quality of the code? :-) -- WARNING: You are logged into reality as root.	[reply]
Re^3: If it is not a core module, then what is it? by philcrow (Priest) on Sep 29, 2006 at 14:55 UTC
Out house code just started as the opposite of in house code, but as soon as I said it in the office everyone realized the benefit of the term, since it suggests aromas that tend to eminate from such code. Phil	[reply]