Re: The Perl 6 Summary
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 18 August 2003 10:29 am, Piers Cawley wrote: Packfile fun So long assemble.pl, it's been good to know you. http://xrl.us/puu Google gives me an error on this: Unable to find thread. Please recheck the URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/QT2Xx533NjVSos4RAh0IAKCl0G9i1qfOKk1/ex98afUhIv96qgCbB4DL Rg56ptBwVdgylGCwhQO2HVI= =Jk9W -END PGP SIGNATURE-
Re: The Perl 6 Summary
Piers, Regarding your Perl6 Essentials summary: Or, he can write code for IMCC using Parrot Intermediate Language (known as PIR for reasons that aren't entirely clear even to one who has been watching the mailing list since the Parrot project started) I suppose noone has much read the README in languages/imcc PIR is what I named the IMCC language and you are correct in your quote, but I've frequently seen people wondering where the name came from. It isn't really an overlay, it is a compiler with an optimizer and register allocator which just happens to emit PASM. If you have Steven Muchnicks book (spelling?) you will notice it is common to name intermediate languages as something with IR in it (MIR, LIR, HIR). Hope that answers your trivia. I suppose I could have provided some more explanation (I haven't read the book yet) but as the original author of IMCC PIR, I wasn't even contacted out of courtesy to write the chapter and was informed after the book was finished. :/ This has been a major stumbling block for me in getting back the motivation to help with Parrot again. -Melvin
Re: The Perl 6 Summary
MS == Melvin Smith [EMAIL PROTECTED] writes: MS I suppose I could have provided some more explanation (I haven't MS read the book yet) but as the original author of IMCC PIR, I MS wasn't even contacted out of courtesy to write the chapter and was MS informed after the book was finished. :/ MS This has been a major stumbling block for me in getting back the MS motivation to help with Parrot again. even though it is not my place as i had nothing to do with the book, i want to apologize for all for the oversight and slight. my impression is that the book authors didn't consult with many of the parrot/p6 people since it would have slowed down writing and production and they were on a very tight schedule. AFAIK others who should have been co-authors or should have been consulted were bypassed as you were. and note that it was o'reilly's decision on how they did the book and they are not parrot. so if that helps salve your wound, i am sure you contributions (past and future) to parrot are welcomed and appreciated by the parrot community (pretty much those on these lists) thanx,. uri -- Uri Guttman -- [EMAIL PROTECTED] http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs http://jobs.perl.org
Re: The Perl 6 Summary
Robin Berjon [EMAIL PROTECTED] writes: Uri Guttman wrote: MS == Melvin Smith [EMAIL PROTECTED] writes: MS This has been a major stumbling block for me in getting back the MS motivation to help with Parrot again. so if that helps salve your wound, i am sure you contributions (past and future) to parrot are welcomed and appreciated by the parrot community (pretty much those on these lists) I second that. The imperatives of book production are mercantile, and have nothing to do with one's excellent participation in an Open Source effort, irrespective of the quality that a given editor may normally have. I'm certain that when a more definitive book is started, there will be much more time to ask all the interesting people for input. Please don't lose your motivation :) Speaking of books. I keep mulling over the idea of attempting to write a 'Soul of a New Machine' type book for Parrot and Perl 6...
Re: The Perl 6 Summary
Uri Guttman wrote: MS == Melvin Smith [EMAIL PROTECTED] writes: MS This has been a major stumbling block for me in getting back the MS motivation to help with Parrot again. so if that helps salve your wound, i am sure you contributions (past and future) to parrot are welcomed and appreciated by the parrot community (pretty much those on these lists) I second that. The imperatives of book production are mercantile, and have nothing to do with one's excellent participation in an Open Source effort, irrespective of the quality that a given editor may normally have. I'm certain that when a more definitive book is started, there will be much more time to ask all the interesting people for input. Please don't lose your motivation :) -- Robin Berjon [EMAIL PROTECTED] Research Engineer, Expwayhttp://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
Re: The Perl 6 Summary
On Mon, Jul 21, 2003 at 03:20:26PM +0100, Piers Cawley wrote: Acknowledgements, Announcements and Apologies First of all, I plead insanity for my mistake of last week's summary. PONIE does not stand for 'Perl On New Internal Architecture', it obviously stands for 'Perl On New Implementation Engine'. I'm very, very sorry and I'll try not to do it again. Actually, Ponie stands for Perl on new Internal Engine. :-) http://opensource.fotango.com/ponie/ponie-faq.html Z.
Re: The Perl 6 Summary
Adam Turoff [EMAIL PROTECTED] writes: On Mon, Jul 21, 2003 at 03:20:26PM +0100, Piers Cawley wrote: Acknowledgements, Announcements and Apologies First of all, I plead insanity for my mistake of last week's summary. PONIE does not stand for 'Perl On New Internal Architecture', it obviously stands for 'Perl On New Implementation Engine'. I'm very, very sorry and I'll try not to do it again. Actually, Ponie stands for Perl on new Internal Engine. :-) http://opensource.fotango.com/ponie/ponie-faq.html Maybe I should make this the new running joke.
