From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Mikhail Senkov" <zloyrobot@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Error recovering in CamlP4
Date: Thu, 8 Feb 2007 14:19:35 +0100 [thread overview]
Message-ID: <cd67f63a0702080519gde5f55at8c994b12dccca2f0@mail.gmail.com> (raw)
In-Reply-To: <503db7bf0702080515kc23e933ma3c404fab9edd81e@mail.gmail.com>
On 2/8/07, Mikhail Senkov <zloyrobot@gmail.com> wrote:
> Hello Caml List.
Hello,
> I have a question. Camlp4 stops parsing at the first
> syntax error.
Yes but with an helpful error message :)
> Is it planning to add error recovering to Camlp4? And if
> it is not in plan, can you propose best way to do it?
I think that Camlp4 is already complex and that's not a good idea to
add such a mechanism.
And it's not in plans at all.
Cheers,
--
Nicolas Pouillard
prev parent reply other threads:[~2007-02-08 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 13:15 Mikhail Senkov
2007-02-08 13:19 ` Nicolas Pouillard [this message]
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=cd67f63a0702080519gde5f55at8c994b12dccca2f0@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=zloyrobot@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).