Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] Information hiding: how to handle module's private static variables in Frama-C?

  • Subject: [Frama-c-discuss] Information hiding: how to handle module's private static variables in Frama-C?
  • From: dmentre at linux-france.org (David MENTRE)
  • Date: Wed, 27 Nov 2013 14:20:12 +0100
  • In-reply-to: <5295C6A8.9050703@cea.fr>
  • References: <CAC3Lx=bqpi2v3cwLZ1bKeWPm262vt+44Ocw1DvQoh1OkGSLQhA@mail.gmail.com> <5295C6A8.9050703@cea.fr>
Hello,

2013/11/27 BAUDIN Patrick <Patrick.Baudin at cea.fr>:
> The ACSL importer plug-in (used to import external ACSL file) takes care of
> that situation.
> Unfortunately, this plugin isn't free.

Even if this plug-in is not available, how one would use this plug-in
to solve this issue?

> Without it, your code have to be transformed.

This is what we have done. I just wanted to be sure that we hadn't
missed another Frama-C feature or trick.

Best regards,
david