At 09:58 PM 2/5/2001 +0000, Tim Bunce wrote:
>On Mon, Feb 05, 2001 at 11:35:59AM -0500, Dan Sugalski wrote:
> > At 02:17 PM 2/5/2001 -0200, Branden wrote:
> > > > I think that, if you want this behavior, a module that implements it
> > > > would be just fine. (Why muck with "use"?) To use a module name
> > > > that seems like it could fit this purpose:
> > > >
> > > > use autoload { Bar => 'http://www.cpan.org/modules/Bar' },
> > > > { Baz => 'ftp://my.local.domain/perl-modules/Baz',
> VERSION =>
> > >2 };
> > >
> > >Very good idea indeed!!! Append the wishlist to add this module to perl6's
> > >standard library!!!
> >
> > Very *bad* idea. It sounds nice, but using a remote module without any
> sort
> > of control is just begging for trouble.
>
>True. But perl6 shouldn't stand in the way of making silly things possible.
I'm fine with silly things, it's dangerous things I don't much care for.
Which isn't to say I'm against loading remote program code, I just think
this isn't the way to do it.
If we can manage to get some sort of safe sandbox (say, Safe compartments
that are reasonably trustable) or we extend the tainting mechanism some to
make these fatal errors unless run with the -U switch or something, I'm
less not OK with that. (I still don't like remote module loading like this,
but it beats the equivalent of putting your system password into the login
banner....)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
