Re: WIP: asciidoc replacement
- From
Wincent Colaiuta <win@wincent.com>
- Date
- Oct 3, 2007, 06:40 UTC
- Message-ID
- <06B9DBA8-596F-4576-8995-8044EA714384@wincent.com>
- In-Reply-To
- <4702F6BB.60908@vilain.net>
El 3/10/2007, a las 3:56, Sam Vilain escribió:
Show 6 quoted lines
> However I have a suspicion that your script is doing line-based > parsing > instead of recursive descent; I don't know whether that's the right > thing for asciidoc. It's actually fairly easy to convert a grammar to > code blocks using tricks from MJD's _Higher Order Perl_. Is it > necessary for the asciidoc grammar?
I haven't looked at all of the asciidoc source for the Git documentation but I suspect that almost all of it is entirely regular, and if there is any nesting in it is is probably of a limited scope (ie. sections, subsections, subsubsections in the user manual) and so you can avoid the complexity of a full recursive descent parser. I'd also expect Johannes' approach to be faster (is it faster than the existing tool chain? I would expect so).
Cheers, Wincent