>Several OS's Perl supports prefer case insensitive file systems
>(obscure ones, like Windows and MacOS ;).
They're broken. We know that.
>On top of that, currently "use Shell" and "use shell" both mean to use
>SHELL.PM (or shell.pm, Shell.pm, sHeLl.pM) on case insensitive file
>systems.
T
On Wed, 13 Sep 2000, Michael G Schwern wrote:
...many good points, all of which I should have known. :-(
I will modify the RFC to reflect that /\bshell\b/i is a poor name, due
to the current Shell module.
Personally, I don't particularly care what it's called - after all, I
don't name things ve
On Wed, Sep 13, 2000 at 07:48:23AM -0400, Bryan C . Warnock wrote:
> On Wed, 13 Sep 2000, Michael G Schwern wrote:
> > Sooo... what happens to the existing Shell.pm?
>
> The RFC title notwithstanding, the pragma would be, by convention,
> lowercase. (As reflected in the abstract.)
The nasty abi
Today around 6:25am, Michael G Schwern hammered out this masterpiece:
: Sooo... what happens to the existing Shell.pm?
Indeed. Especially since, as of 5.7.0, it has a beautiful OO Interface so name
space pollution is avoided*. ;-)
[*] Of course, the origional intention of Shell.pm, seemingly t
On Wed, 13 Sep 2000, Michael G Schwern wrote:
> Sooo... what happens to the existing Shell.pm?
The RFC title notwithstanding, the pragma would be, by convention,
lowercase. (As reflected in the abstract.)
Of course, should language features be added to allow scoping to be
easily controlled, it
Sooo... what happens to the existing Shell.pm?
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
MORONS!
