Front page | perl.bootstrap |
Postings from July 2000
On Mon, Jul 24, 2000 at 06:55:46PM -0700, chip@valinux.com wrote:
> According to horos:
> > Include keyword 'open' in perl library? [y]
> > Include support for 'http' in 'open' [y]
> > Include support for 'ftp' in 'open' [y]
> > Overload 'open' with other support (https, etc)? [n];
> >
> > Include keyword 'close' in perl library? [y]
> > Include keyword 'select' in perl library? [y] n
>
> One point against: The more of Perl that's optional, the more Perl
> programs become non-portable -- perhaps by accident.
Counterpoint: in the last few project that I done, I've built a custom
version of perl specifically for the project. I don't care about
running every script imaginable on this perl install. I only care about
the perl related to the project. I think this model of development is
going to become more common. I envision at least two perl branchings:
generic perl -- a unix utility for sysadmins, random scripts
applcation specific perl -- a custom built version for a specific project
--
Never ascribe to malice that which can be explained by stupidity.
(via, but not speaking for Deutsche Bank)