develooper Front page | perl.bootstrap | Postings from July 2000

Re: Working Group Proposal

From:
horos
Date:
July 24, 2000 18:30
Subject:
Re: Working Group Proposal
> I agree, but I'd think something along the other end of the spectrum:
> 
> $ ./configure --remove-functionality
> *** WARNING: If functionality is removed from this binary, some 
> existing Perl6 Applications may not function properly or at all with 
> this binary. This optionis recommended only for experts who have a 
> very good grasp of what they are doing. Are you sure you wish to 
> proceed? [n] Y
> ** OK, YOU ASKED FOR IT.
> Remove keyword 'open' from perl library? [n]
>    Include support for 'http' in 'open'? [y]
>    Include support for 'ftp' in 'open'? [y] N
> ** FTP SUPPORT IN OPEN REMOVED **
> 

Ok, but you also need the ability to *add* functionality as well:

configure --add-functionality
*** WARNING: If functionality is added to this binary, some 
existing Perl6 Applications may not function properly or at all with 
this binary. This optionis recommended only for experts who have a 
very good grasp of what they are doing. Are you sure you wish to 
proceed? [Y]

add which runtime modules [ strict warn ] Carp (qw(cluck));

which would then do an implicit 'use strict;' 'use warn', and 'use Carp'
at the beginning of each package.

and perhaps the ability to totally customize your functionality:

configure --use-configuration perl5compatability 

And, building on an idea that Joshua had

gen_perl perl5compatability ./perl5.tar.gz

where gen_perl is in microperl, takes the perl5compatability file, downloads
all the necessary stuff for making perl6 compatibile with perl5, deletes all
the cruft, and creates perl5.tar.gz

Ed

Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About