Front page | perl.bootstrap |
Postings from July 2000
I'll just say that "I disagree". I don't think you should EVER have to recompile your perl binary to get something a program author thought would be available in THEIR perl binary. A perl program should work "anywhere" unless the end-user has explicitly removed functionality from his/her perl-binary. Again, my $0.02 worth. D At 6:30 PM -0700 7/24/00, horos wrote: > >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