Front page | perl.perl5.porters |
Postings from July 2006
> I asked Marc what core support Coro would ideally need, which is what prompted > him to mail p5p some months back (and bad me for not commenting on thread). > I don't think that Coro necessarily should go in (and the pre-requisite of > "support" needs to be addressed as described in > http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2006-06/msg00946.html ) Interesting. All I have to say is that it's got to be easier to support a young language than a mature one. Young langauges behave less than ideally due to incompleteness; mature ones due to attempts at completeness; one of those is a lot harder than the other to fix. It could be said that the users create bugs by creating the various scenarios, and having users means having bugs. Take the QuickSort int32 wrap bug for instance... You're not supporting the language or interpreter so much as you're supporting the vast number of users and uses of it. And for that, all I can suggest is a code dungeon... where promising prospects are imprisoned and bribed to code with slightly upgraded rations. -scott