caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Kerneis <gabriel@kerneis.info>
To: David MENTRE <dmentre@linux-france.org>
Cc: Xavier Rival <Xavier.Rival@ens.fr>,
	caml users <caml-list@inria.fr>,
	ocaml-jobs@inria.fr
Subject: Re: [Caml-list] [ocaml-jobs] Developper position: designing a C front-end in OCaml
Date: Tue, 15 Oct 2013 14:22:16 +0100	[thread overview]
Message-ID: <20131015132216.GC7090@kerneis.info> (raw)
In-Reply-To: <CAC3Lx=abf-PJWAPM=KS57bhsFZj==Hi5Uia7xZH4NTjFt6Oyxw@mail.gmail.com>

On Tue, Oct 15, 2013 at 03:02:23PM +0200, David MENTRE wrote:
> In that case, why don't you extend CIL to fix its deficiencies? It

We are talking about changing the AST used to manipulate the programs.
Changing it (in either CIL or Frama-C) would mean breaking every
existing code around the world based on it.  While it might be
acceptable in some cases, it is definitely a major change, with the risk
of alienating the user base.  And if breaking changes are required
anyway, restarting from scratch might be cleaner.

> would help other projects using CIL like Frama-C.

It would not help Frama-C, because they forked CIL and changed it too
deeply to port anything but trivial patches between them.

> In the same way, why do you implement your own C parsing
> infrastructure and do not build a Frama-C plug-in for your analysis?

Frama-C uses (almost) the same AST as CIL, with the same simplifying
assumptions that make CIL unsuitable for Xavier.

> [1] I am maintaining this directory:
>     http://gulliver.eu.org/free_software_for_formal_verification

Thanks for the link.  You should update the entry about CIL:
http://gulliver.eu.org/program_dev_check_environments#cil
to the new URL:
http://cil.sourceforge.net/

Best regards,
-- 
Gabriel Kerneis (CIL maintainer)

  reply	other threads:[~2013-10-15 13:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 12:31 [Caml-list] " Xavier Rival
2013-10-15 12:41 ` Gabriel Kerneis
2013-10-15 12:48   ` [Caml-list] [ocaml-jobs] " Xavier Rival
2013-10-15 12:52     ` Julia Lawall
2013-10-15 13:02     ` David MENTRE
2013-10-15 13:22       ` Gabriel Kerneis [this message]
2013-10-15 18:29         ` Dmitry Grebeniuk
2013-10-15 21:36           ` Gabriel Kerneis
2013-10-16  0:12             ` Wojciech Meyer
2013-10-16  6:12         ` David MENTRE
2013-10-15 18:13     ` Florian Weimer
2013-10-15 14:06 ` [Caml-list] " Basile Starynkevitch
2013-10-15 15:36   ` Wojciech Meyer

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=20131015132216.GC7090@kerneis.info \
    --to=gabriel@kerneis.info \
    --cc=Xavier.Rival@ens.fr \
    --cc=caml-list@inria.fr \
    --cc=dmentre@linux-france.org \
    --cc=ocaml-jobs@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;
as well as URLs for NNTP newsgroup(s).