Said Jarkko Hietaniemi <[EMAIL PROTECTED]>: > Much of the recent furor would have been gone or diminished if the > FreeBSD tool had not been /usr/bin/perl.
Sure, but history. We can't do anything about that. > /usr/bin/perl is both by > documentation and by tradition a contract saying: "Hi, I'm the full > Perl, you can use me". I never read it that way. I've never seen anything saying that use of the core language means you have to swallow the libraries as well. > Well, modulo Perl releases, of course, so it's > more like saying "Hi, I'm one of the official Perls, you can use > me."-- and official Perls do include the respective modules. My reading is that official perls _happen_to_ include the respective modules. It is with some dismay that I discover that this is not the case, but I am heartened by another direction. That direction is the one suggesting that perl should be split into "base perl" + "standard libraries", with the ability to install only "base" into an OS with the libraries as an option. Having the libraries as part of the base language for Perl makes about as much sens to me as making glibc a part of C or Microsoft's Foundation Classes a part of C++. You may _need_ these things, but they are separate entities. M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn #text/plain; name=cv.doc [Mark Murray CV Plain Text] cv.doc #application/octet-stream; name=cv.pdf [Mark Murray CV PDF] cv.pdf
