Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

Re: Re: Re: Re: Re: Re: Ensuring forward compatibility

by kelan (Deacon)
on Apr 15, 2004 at 18:28 UTC ( [id://345491] : note . print w/replies, xml ) Need Help??


in reply to Re: Re: Re: Re: Re: Ensuring forward compatibility
in thread Ensuring forward compatibility

I would personally have no problem doing something like this (or even recommending it to a supervisor if Perl 6 were being considered), but I can picture a lot of people grumbling if Larry were to mandate it as The Way Forward.

Again, I support a move like this that would separate the binary names. It would make the whole "How do we decide if it's Perl 5 or 6?" question moot. It's the masses that I imagine are (or would be) opposed to the idea that are keeping us in this mess.

  • Comment on Re: Re: Re: Re: Re: Re: Ensuring forward compatibility

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Re: Re: Ensuring forward compatibility
by Vautrin (Hermit) on Apr 15, 2004 at 20:57 UTC
    I'm just pointing out that it doesn't have to be done by the development team. I plan on using the above script, or one similar to it, to separate Perl 5 and Perl 6 for some time to come. Of course, I suppose you need to know that you can change what the Perl Binary is installed as in the ./configure script in order to do this. Perhaps it would make sense for this to be the standard in the installation. It wouldn't be hard for people creating new code to point to /usr/bin/perl6, and it would be very easy for the Perl compiler to differentiate between Perl 5 and Perl 6

    Want to support the EFF and FSF by buying cool stuff? Click here.