Nathan Torkington wrote: > Alan Burlison writes: > > seem a very optimal way to go about it. How about a design document > > (format to be decided) and a 'design + commentary' document which is the > > design document with the condensed email discussion inserted into it as > > the commentary. That way there is a design spec for the implementation, > > Cool. You're volunteering to edit it? Hah! You don't ensnare me that easily, Mr. Torkington! ;-) How about writing the documents in XML and having a 'perl specification' DTD? With a bit of careful thought we will be able to do all sorts of interesting stuff - for example if we tag function definitions we can start cross-checking other documents and even the code for consistency with the spec. Death to POD! Alan Burlison
- Re: Proposal for groups Ask Bjoern Hansen
- Re: Proposal for groups Simon Cozens
- Designers step forward now Nathan Torkington
- Re: Proposal for groups Alan Burlison
- Re: Proposal for groups Simon Cozens
- Re: Proposal for groups Jarkko Hietaniemi
- Re: Proposal for groups Adam Turoff
- Re: Proposal for groups Jarkko Hietaniemi
- Re: Proposal for groups Alan Burlison
- Re: Proposal for groups Nathan Torkington
- Re: Proposal for groups Alan Burlison
- Re: Proposal for groups Adam Turoff
- Re: Proposal for groups Alan Burlison
- Re: Proposal for groups Simon Cozens
- Re: Proposal for groups Tim Bunce
- Re: Proposal for groups Simon Cozens
- Re: Proposal for groups Nathan Torkington
- Markup wars (was Re: Proposal ... Bennett Todd
- Re: Markup wars (was Re: Propo... Nathan Torkington
- Re: Markup wars (was Re: Propo... Russ Allbery
- Re: Markup wars (was Re: Propo... Jarkko Hietaniemi