Re: Re: Why Perl does not support database access through core modules?

I got my list of what's in the core from http://www.perldoc.com/perl5.8.0/lib.html, which, to me, implies what's supposed to be in the core for 5.8.x. I checked my copy of 5.8.2 and it includes files not on that list (as well as not having files on that list). Files not on that list that I wouldn't think should be in the core include:

Filter::Simple (is it used by other core modules?)
Hash::Util (same criteria as Scalar::Util and List::Util)
Storable and FileCache
Getopt:: (Is it used by some Makefile.PL's?)
MIME::
Digest::MD5 (unless it's needed by CPAN)
Data::Dumper (this is borderline, IMHO)
User::

The dbmopen support in perl5 ... Personally, I think that dbmopen and friends should be treated as locked is with Threads. If you use the module, you get the keyword, otherwise it's not reserved. I think that would be an acceptable compromise, but, then again, I've never used (or seen used) dbmopen and friends in my experience.

I would suggest an additional cleanup activity - removal of all reserved words that require an additional module to work. locked() isn't a reserved word in the core ...

------
We are the carpenters and bricklayers of the Information Age.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

Comment on Re: Re: Why Perl does not support database access through core modules?

Replies are listed 'Best First'.
Re: Why Perl does not support database access through core modules? by Abigail-II (Bishop) on Jan 21, 2004 at 16:41 UTC
To me, perldoc.com looks like an outdated website from an individual (Carlos Ramirez) who is totally unknown to me. I wouldn't take his list as something that is supposed to be in perl 5.8.x. Having said that, I agree that most of the modules you list shouldn't have been in the core distribution. (Digest::MD5 is used by CPAN; Data::Dumper is probably tied into the internals tightly enough that it wouldn't survive outside the core distro). The dbmopen support in perl5 ... Personally, I think that dbmopen and friends should be treated as locked is with Threads. If you use the module, you get the keyword, otherwise it's not reserved. I think that would be an acceptable compromise, but, then again, I've never used (or seen used) dbmopen and friends in my experience. That's out of the question. Backwards compatibility is important. dbmopen/dbmclose have been available since at least perl-4.0.0 (which dates from 1991), probably even before that. There's not much gain in removing the keywords. locked() isn't a reserved word in the core ... Nope; but `lock` is. Abigail	[reply] [d/l]

Replies are listed 'Best First'.

Re: Why Perl does not support database access through core modules?
by Abigail-II (Bishop) on Jan 21, 2004 at 16:41 UTC

The dbmopen support in perl5 ... Personally, I think that dbmopen and friends should be treated as locked is with Threads. If you use the module, you get the keyword, otherwise it's not reserved. I think that would be an acceptable compromise, but, then again, I've never used (or seen used) dbmopen and friends in my experience.

locked() isn't a reserved word in the core ...

lock

Abigail

[reply]
[d/l]