From: "Mike Lin" <mikelin@MIT.EDU>
To: "John Max Skaller" <skaller@ozemail.com.au>,
"Gerd Stolpmann" <info@gerd-stolpmann.de>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml-3.05: a performance experience
Date: Mon, 5 Aug 2002 12:24:07 -0400 [thread overview]
Message-ID: <021e01c23c9c$86d0c9b0$240f2744@cc1003186f> (raw)
In-Reply-To: <3D4E972D.6000706@ozemail.com.au>
> I'm intrigued by the relationship between these two parsers. In
particular,
> note that my Felix compiler takes 'pull' code, and automatically
> translates it
> to the much more efficient 'push' model: ie. it switches the client/server
> relationship around, a process I call control inversion.
I'm just curious if you could elaborate on in what respect a push parser is
"much more efficient"? From my experience pull parsers tend to be easier to
use because they don't impose an event-driven model on the driver program,
and also it is trivial to build a push parser on top of a pull parser.
-Mike
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-08-05 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 3:33 Alexander V. Voinov
2002-08-03 12:33 ` Gerd Stolpmann
2002-08-03 17:27 ` [Caml-list] OCAMLRUNPARAM=b David Fox
2002-08-04 2:50 ` [Caml-list] ocaml-3.05: a performance experience Alexander V. Voinov
2002-08-04 20:45 ` Gerd Stolpmann
2002-08-05 15:18 ` John Max Skaller
2002-08-05 16:24 ` Mike Lin [this message]
2002-08-05 16:53 ` Alexander V.Voinov
2002-08-06 3:22 ` John Max Skaller
2002-08-06 13:24 ` Mike Lin
2002-08-06 11:10 ` Noel Welsh
2002-08-06 12:56 ` Andreas Rossberg
2002-08-04 18:06 Damien Doligez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='021e01c23c9c$86d0c9b0$240f2744@cc1003186f' \
--to=mikelin@mit.edu \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=skaller@ozemail.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox