From: Bryan C. Warnock [mailto:[EMAIL PROTECTED]] > > If you don't already know whether it exists, or how it will > roughly work (lexically), you shouldn't be discussing it on > p6d. Kicked back to p6l. [...] > and again... what's the scope of p6d
p6d exists to document the language. A task which consists of going over the A&E's and Larry's posts to p6l, etc. and flushing them out into deliverables: o Perl6/Parrot regression tests o Language Specification derived from tests o Core Perl Documentation / User Manual Flushing them out consists of: o disambiguation o isolating potential problems o writing tests and documentation I have difficulty separating the pd6 disambiguation discussions from language design... as I expect do others. Language design discussion belongs on p6l. And I for one, would like to see a big red flag delimiting speculation, when it occurs on p6d. Though there's the p6d argument that a limited amount of speculation is called for, in that we should use the p6d cabal to work our language design issues into a coherent refined proposal before dumping them into the fray that is p6l. > , and how does it differ from p6l? p6d differs from p6l, in that p6d has a specific goal: "document the language". Whereas p6l is a rather more ambiguous forum for people to influence Larry's design and explain it one another. That said, it is also hoped that p6d will also have a beneficial effect on p6l. Where p6l undergoes an iterative wave of questions and proposals re-examining issues covered in previous A&E's following each new release, p6d hopes to annotate its documentation to include the various trade-offs involving alternative syntax, semantics, implementation impacts, ideological ax grinding, etc. so that p6l can refer people to the old arguments instead of wasting ever more time on them. -- Garrett Goebel IS Development Specialist ScriptPro Direct: 913.403.5261 5828 Reeds Road Main: 913.384.1008 Mission, KS 66202 Fax: 913.384.2180 www.scriptpro.com [EMAIL PROTECTED]
