Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Spiros Eliopoulos <seliopou@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: angstrom
Date: Mon, 25 Jul 2016 12:07:18 -0400	[thread overview]
Message-ID: <CAEkQQgK-=6Z-mrakRwfLpQJV7-fHn588EgbC7aHVb80tdhFpcg@mail.gmail.com> (raw)
In-Reply-To: <169BD7F8D4244E4DBEA9861FD6EDFB00@erratique.ch>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Mon, Jul 25, 2016 at 11:44 AM, Daniel Bünzli <daniel.buenzli@erratique.ch
> wrote:

> Le lundi, 25 juillet 2016 à 16:15, Spiros Eliopoulos a écrit :
> > If the client will always accept any parse correction from the parser,
> then it should accumulate all errors and return them along with the parse
> result.
>
> No, in practice you want to be able to report errors before having seen
> all the input.


So in this situation, the main parse succeeds with errors corrections that
are going to be logged somewhere. If something besides logging would be
done with the errors, it would fall into one of the other cases described
above. The latency difference is on the order of milliseconds, maybe
seconds, depending on the application. It's not nearly enough time to make
a difference in whatever log analysis process they would be fed into,
whether it's inspection by a human (certainly) or some other automated
process (they all typically include a ton of latency already).

-Spiros E.

[-- Attachment #2: Type: text/html, Size: 1390 bytes --]

  reply	other threads:[~2016-07-25 16:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 13:35 Spiros Eliopoulos
2016-07-22 14:38 ` Daniel Bünzli
2016-07-22 21:46   ` Spiros Eliopoulos
2016-07-23  2:17     ` Daniel Bünzli
2016-07-23  6:41       ` Cole Brown
2016-07-23 11:37         ` Daniel Bünzli
2016-07-25 14:15       ` Spiros Eliopoulos
2016-07-25 15:44         ` Daniel Bünzli
2016-07-25 16:07           ` Spiros Eliopoulos [this message]
2016-07-25 16:21             ` Daniel Bünzli
2016-07-25 19:37               ` Spiros Eliopoulos
2016-07-25 20:03                 ` Daniel Bünzli
2016-10-13 12:42 ` Anil Madhavapeddy
2017-02-03 19:37 ` Hendrik Boom
2017-02-04 16:36   ` Spiros Eliopoulos

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='CAEkQQgK-=6Z-mrakRwfLpQJV7-fHn588EgbC7aHVb80tdhFpcg@mail.gmail.com' \
    --to=seliopou@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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