From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,50e705cdf2767cc6
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news4.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Natasha Kerensikova <lithiumcat@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Parser interface design
Date: Thu, 7 Apr 2011 18:56:37 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <slrnips275.2fnq.lithiumcat@sigil.instinctive.eu>
References: <slrnipof32.2fnq.lithiumcat@sigil.instinctive.eu>
 <4d9c59da$0$7664$9b4e6d93@newsspool1.arcor-online.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 7 Apr 2011 18:56:37 +0000 (UTC)
Injection-Info: mx03.eternal-september.org;
 posting-host="Mda950WjNwNLAFOE7yJXQw";
	logging-data="5847"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+f9nO7UK7cYoxS4ZrwwQRU"
User-Agent: slrn/0.9.9p1 (FreeBSD)
Cancel-Lock: sha1:Ic6SLpIi61fZK0LhUEdYxazHvnU=
Xref: g2news2.google.com comp.lang.ada:19679
Date: 2011-04-07T18:56:37+00:00
List-Id: <comp.lang.ada>

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