On Tue, Nov 05, 2013 at 11:00:59AM -0600, Patrick R. Michaud wrote: > > Forking the documentation, or creating derivative works, shouldn't be a > > problem, as long as it doesn't change the specification in itself, and > > thereby create confusion regarding what the Perl 6 specification is. > > ...and this is the exact reason for that wish. The documentation isn't > the specification at all -- the test suite is.
I should probably clarify. I think that referring to the Synopses as "specification" *increases* confusion on the issue, because it's the test suite that defines the language, not the Synopses. In some sense, perhaps the Synopses should be considered just another (human-readable prose) "implementation" of Perl 6. Just like any other Perl 6 implementation, a discrepancy between the Synopses and the test suite means that one of them needs updating (based on experience and evolution), but ultimately it's the test suite that determines what is or is not correct in the Perl 6 specification. Pm