Hi folks,
I thought I'd give an update on what has been going on w.r.t. SerAPI and
its successor.
First, we added a bit of documentation, it is not a wonder, and
moreover, it will change, but here it is:
http://ejgallego.github.io/coq-serapi/priv-serapi/Serapi_protocol/
The main change is that
> This little detail will likely end up forcing the Elisp side to either
> re-implement a sexp-reader by hand (in Elisp, which will be slowish),
> or require ugly hacks to try and pre-process the answer before passing
> it to the sexp reader (or post-process the sexp), which will likely
> always
Hi Stefan!
Stefan Monnier writes:
> Looking at SerAPI, I'm wondering about the choice of "sexp". I know it
> may sound odd to want something else than sexps when working in Elisp,
> but in reality sexps only work well if they use *exactly* the same
> syntax. E.g. in
Looking at SerAPI, I'm wondering about the choice of "sexp". I know it
may sound odd to want something else than sexps when working in Elisp,
but in reality sexps only work well if they use *exactly* the same
syntax. E.g. in https://github.com/ejgallego/coq-serapi I see:
(Query ((sid 3) (pp
