On Fri, 2002-12-27 at 12:59, Rich Morin wrote:
> I think that this is a very interesting approach, providing a formal
> framework for the IETF notion of "rough consensus and running code".
I like that phrase--"rough consensus and running code."
> The tension I see between Brian and Oren's comments (test code vs.
> EBNF, roughly) points out the fact that a language specification may
> be used in any of several tasks:
> writing (and testing!) a new parser
> writing application code to generate the language
> learning the features of the language
> debugging applications which use the language
> I would like to see the proposed wiki take these roles into account.
You say "proposed" as if the YAML Wiki hasn't already existed for six
There's a lot of good material out there, but it's not necessarily
organized for newcomers or potential porters. Being a Wiki, though,
there's nothing to stop folks from reorganizing the material as needed.
Folks can also copy material to non-Wiki tutorials, etc., with the
> So, for instance, there should be provision for EBNF formalisms, test
> code, and example code, as well as descriptive text for each of these.
> In addition, there should be introductory text, definitions, and other
> supplementary documentation.
> Then, using the hypertext capabilities of the wiki, the pages should
> link to related documents. Without overly constraining the wiki, I'd
> like to see a document plan that describes the format and function of
> each type of page that one should expect to find in the wiki. This
> plan should be part of the wiki, with links to exemplary pages.
Don't let us stop you. :)
Seriously, it's a public Wiki, feel free to contribute.
author of PyYaml