I didn't know about the pugs docs, that's really helpful. I would say the synopses are awesome. It is like reading one of those Programmers Notes ORA books but even more to the point. The only problem I see, is that the corner cases aren't explained very well, and that is very apparent when you watch the other mailing lists. And then there are a few portions that say something to the effect of "We may change this if..." or "It may be useful down the road to relax this..." which can mean a significant difference in how you approach particular problems, but overall, it's good stuff. I am going to start tinkering and porting some of my p5 code over just to get a feel for it and see if I come across any of those odd corner cases so I can help out or offer an opinion.
BTW, I think this list is a fantastic idea. On 5/18/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote:
Hallo Thomas :-), * Thomas Wittek <[EMAIL PROTECTED]> [2006-05-18 20:30]: > Would you recommend reading the synopses[1]? > Or should I take a look at pugs-doc? the synopses are the canonical design documentation of the Perl 6 language, to my understanding. Pugs-doc would probably be a good place to look if you actually want to tinker in the language (at least, in its Pugs incarnation). There's a `getting_started`[1] in pugs-doc that should provide the sort of pointers you're after. [1]: http://svn.openfoundry.org/pugs/docs/getting_started Regards, -- #Aristotle *AUTOLOAD=*_;sub _{s/(.*)::(.*)/print$2,(",$\/"," ")[defined wantarray]/e;$1}; &Just->another->Perl->hacker;
