On Wed, Jul 30, 2008 at 11:13:14PM -0400, Bob Rogers wrote: ... > Much has changed since the second edition was published, so the book is > likely to be misleading in some places, and dead wrong in others. But > since I only have a copy of the first edition, I'm afraid I can't be > more specific. > > As an alternative for Parrot, you may prefer to start with the > documentation in the source repository [1], which is more up-to-date > (with some glaring exceptions), though easier to get lost in. For > learning about Perl 6 itself, the Synopses [2] are the most up-to-date > statements of the language design, and are fairly stable now; I've been > grinding my way through them myself, though I find it slow going.
Okay, it sounds like that's a better way to go for now. Thanks. Maybe whenever Learning Perl 6 comes out that should be my first Perl 6 book. > > If you would like to contribute, then you'll need to get your hands > dirty with the living documentation sooner or later. If your interest > is casual, then the overview the book provides is probably worth the > errors in detail. > > Out of curiousity, is your interest primarily in Perl 6, Parrot, or > both? > I'd say Perl 6 first of all. I've read a little bit in the Synopses and Apocalypses and really liked what I saw, although I can't remember most of it now or form any kind of cohesive picture of how to combine the features into programs. But I'm also interested in Parrot in a general way (I like the thought of contributing but I'm doubtful I'll end up helping given my background and, uh, work ethic, I guess would be the phrase). I found your presentation to the group earlier in the year very interesting. I'm also interested in Pugs, but thought I should start by trying Rakudo, especially since I wasn't sure if Pugs is continuing to be developed. Right now I have this simple little program I want to write, just a UI (or more likely a command line interface initially) on top of a small sqlite db. I thought it would be fun to use it as an exercise to start learning Perl 6 and to see how far along things are in the Parrot implementation. So when I have some picture of Perl 6's features I figured I'd start writing it and see how it goes. If it turns out Parrot hasn't yet implemented a feature I choose, that's fine. It isn't a project that has to ever be finished, necessarily. Maybe I could try to read the Parrot source code and understand why whatever I tried didn't work and what's not there yet, which I figured would be educational. -- Mike Small [EMAIL PROTECTED] _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
