From: "Jocelyn Sérot" <jocelyn.serot@uca.fr>
To: Daniil Baturin <daniil@baturin.org>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Lascar/RFSM & Camlp4 (was camlp4 & OCaml 4.08)
Date: Fri, 5 Jul 2019 11:55:59 +0200 [thread overview]
Message-ID: <FEF8B0A0-0BB5-4130-B6FE-00A202662C8B@uca.fr> (raw)
In-Reply-To: <393603fa-0efa-5714-82da-ba4bc3e869b8@baturin.org>
Hi Danill - and sorry for the late answer.
Yes, Lascar only use camlp4 for stream expressions (using the Genlex to parse small expressions).
I’ve checked, and i cant find any reference to camlp4 in the latest version of Rfsm; i can’t remember why i put it the package dependency list (because it itself depends on Lascar ?).
You’re much welcome to work on path.
Jocelyn
Le 2 juil. 2019 à 11:25, Daniil Baturin <daniil@baturin.org> a écrit :
> Hi Jocelyn,
> Camlp5 is still sort of maintained, but I don't think it's going to be
> developed beyond compatibility updates.
> For syntax extensions, everyone is switching to PPX.
>
> From a quick look, it seems like the only bit of camlp4 you use is
> stream expressions.
> This is one of the things PPX can't do (on purpose, since it doesn't
> allow _arbitrary_ extensions),
> but I don't think just using streams directly is going to make code much
> longer.
>
> Or I missed some other camlp4 bits?
>
> I'm ready to work on a patch if you are open to it.
>
> On 7/2/19 1:44 PM, Jocelyn Sérot wrote:
>> Le 29 juin 2019 à 17:15, Daniil Baturin <daniil@baturin.org> a écrit :
>>
>>> Perhaps we should make some coordinated effort to help them.
>>> I've just sent a pull request to the ocamldot maintainer that enables
>>> the graphviz files parsing and printing modules
>>> to build and work with 4.08. The GTK parts have their own issues.
>>> Next I'm going to look into LASCAR/RFSM (packages that interest me first ;).
>>>
>> Hi Daniil,
>>
>> I’ve been been thinking of removing the dependency of Lascar and RFSM on camlp4 for a while.
>> Is switching to CamlP5 a good alternative ?
>>
>> Jocelyn
>>
>>
>
>
next prev parent reply other threads:[~2019-07-05 9:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 13:45 [Caml-list] camlp4 & OCaml 4.08 Richard W.M. Jones
2019-06-27 17:28 ` Ian Zimmerman
2019-06-27 20:00 ` Richard W.M. Jones
2019-06-27 18:09 ` Jürgen Hötzel
2019-06-29 9:06 ` Anil Madhavapeddy
2019-06-29 9:43 ` Richard W.M. Jones
[not found] ` <12C0FD24-2DCD-4128-B020-84416F228E87@metastack.com>
2019-06-29 10:52 ` Richard W.M. Jones
2019-06-29 17:49 ` Sylvain Le Gall
2019-07-18 14:23 ` Richard W.M. Jones
2019-07-23 8:12 ` Richard W.M. Jones
2019-07-23 16:33 ` Sylvain Le Gall
2019-07-23 16:37 ` Richard W.M. Jones
2019-06-30 8:55 ` David Allsopp
2019-07-01 13:40 ` Jeremie Dimino
2019-07-02 14:30 ` Louis Gesbert
2019-06-29 15:15 ` Daniil Baturin
[not found] ` <5CE377AD-CB06-4261-BD26-A2A697253F02@uca.fr>
[not found] ` <393603fa-0efa-5714-82da-ba4bc3e869b8@baturin.org>
2019-07-05 9:55 ` Jocelyn Sérot [this message]
2019-07-24 15:10 ` [Caml-list] Camlp4-free implementation of stream parsers (was camlp4 & OCaml 4.08) Jocelyn Sérot
2019-07-24 15:31 ` Daniil Baturin
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=FEF8B0A0-0BB5-4130-B6FE-00A202662C8B@uca.fr \
--to=jocelyn.serot@uca.fr \
--cc=caml-list@inria.fr \
--cc=daniil@baturin.org \
/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