From: Dave Mason <dmason@sarg.ryerson.ca>
To: caml-list@inria.fr
Cc: Alex Cowie <cowie@cs.unisa.edu.au>,
STARYNKEVITCH Basile <Basile.Starynkevitch@cea.fr>,
Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Subject: Re: [Caml-list] Different types of streams
Date: Wed, 05 Sep 2001 06:58:59 -0400 [thread overview]
Message-ID: <200109051058.f85AwxM05118@sarg.ryerson.ca> (raw)
In-Reply-To: Your message of "Wed, 05 Sep 2001 11:30:21 +0200." <20010905113021.N5393@verdot.inria.fr>
(I've cc'ed everyone because for some reason my postings rarely make
it to the mailing list, and if they do they take days.)
>>>>> On Wed, 5 Sep 2001 11:30:21 +0200, Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr> said:
> On Wed, Sep 05, 2001 at 06:43:58PM +0930, Alex Cowie wrote:
>> The convenience of having this parsing facility within the Ocaml
>> syntax should not be underestimated particularly for program
>> development under the toplevel.
I want to re-iterate this. I have several 10's of lines of caml code,
and probably 1/2 of the programs I write use the [< >] parsing.
> Under the toplevel, you can #load "camlp4o.cma"
Honestly, I don't really understand the implications of the
preprocessor. If that is literally all I have to do and then I can
use the syntax, that is probably fine (and if it's just as easy from
the command line and for ocamlopt). But I guess I don't understand
why it won't be the default if it's really that trivial.
> Remember that the streams and parsers in OCaml have a very bad
> implementation, not tail recursive and not optimized. We regularly
> receive bug reports about their slowness and stack overflows when
> they are used.
I don't think anyone is arguing against fixing the implementation, but
the [< >] parsers are much more convenient/natural than yacc-like
parsers for many people and purposes. Even a switch that let me
choose LALR or LL parsing but used the same syntax (as some C-based
tools do - see (I think) ANTLR) would seem to address this.
../Dave
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-09-06 9:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-26 18:23 Nicolas George
2001-08-27 9:49 ` Daniel de Rauglaudre
2001-08-27 17:47 ` Nicolas George
2001-08-28 8:20 ` Daniel de Rauglaudre
2001-08-28 9:33 ` Nicolas George
2001-08-29 8:39 ` Daniel de Rauglaudre
2001-09-05 1:03 ` Christian RINDERKNECHT
2001-09-05 7:34 ` Daniel de Rauglaudre
2001-09-05 8:02 ` STARYNKEVITCH Basile
2001-09-05 9:10 ` Daniel de Rauglaudre
2001-09-05 9:13 ` Alex Cowie
2001-09-05 9:30 ` Daniel de Rauglaudre
2001-09-05 10:58 ` Dave Mason [this message]
2001-09-05 12:06 ` Daniel de Rauglaudre
2001-09-05 12:56 ` Dave Mason
2001-09-05 14:01 ` Daniel de Rauglaudre
2001-09-05 13:29 ` Nicolas George
2001-09-05 14:30 ` Patrick M Doane
2001-09-05 14:44 ` Daniel de Rauglaudre
2001-09-05 14:55 ` Patrick M Doane
2001-09-05 19:39 ` Brian Rogoff
2001-09-05 14:49 ` [Caml-list] Camlp4 and CamlIDL in main distribution? Markus Mottl
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=200109051058.f85AwxM05118@sarg.ryerson.ca \
--to=dmason@sarg.ryerson.ca \
--cc=Basile.Starynkevitch@cea.fr \
--cc=caml-list@inria.fr \
--cc=cowie@cs.unisa.edu.au \
--cc=daniel.de_rauglaudre@inria.fr \
/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