| |||||||||||||
A Perl 6 status updateA Perl 6 status updatePosted Jan 2, 2008 2:52 UTC (Wed) by rloomans (guest, #759)In reply to: A Perl 6 status update by dskoll Parent article: A Perl 6 status update Having to completely-different languages given the same name is going to cause harm. I doubt it. If you read: http://dev.perl.org/perl6/doc/design/syn/S01.html You will see that not only is backward compatibility very important, interoperability between Perl 5 and 6 code - even in the same file - is very high on the list. I'm also the maintainer of a couple of CPAN modules (MIME::Tools being the most prominent) and if Perl 6 were called something else, I wouldn't have to port MIME::Tools (which is after all a Perl module.) As I understand it, Perl 5 modules will be perfectly usable from Perl 6 code. The only incentive for using Perl 6 syntax will be if you need it's features. If you don't, don't re-write. Simple. As it is now, if I want to maintain the module, I'm going to owe it to the audience to port it to Perl 6. This is work I don't really need, thanks! I think that you are exaggerating.... Once Perl 6 is deployed you may have reason to complain if there are compatibility issues. As I understand it, your concerns are ones that are very high on the list of the Perl developers' priorites. Please damp the flames a bit.
(Log in to post comments)
|
|||||||||||||