Re: Parser interface design

[Natasha Kerensikova <lithiumcat@gmail.com>]

Hello,

On 2011-04-06, Georg Bauhaus <rm.dash-bauhaus@futureapps.de> wrote:
>  * use a task that serves as an event queue. The task will collect
> parsing events and forward them as necessary.  The parser is then
> completely ignorant of any rendering.

I have absolutely no idea of what it might even remotely look like. I
guess my C past, where task means thread, which means complex and
unreadable and extremely difficult to debug, doesn't help conceiving
what this possibility.

I wouldn't mind a deeper description of this idea, but I don't want to
tax too much of your time.

> As there are several input formats, one might either activate the
> task matching the input format, or make a task exhibit different
> behavior depending on the input format.

I might have been too tainted by my C implementation, but I found then
that attempting to use another input format, even close (like Textile or
Creole), required so much added flexibility and unknowns that I couldn't
find out how to make a defined interface. So I gave up having several
input format (except through several independent projects).


Natasha