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: Patrick.Baudin at cea.fr (BAUDIN Patrick)
  • Date: Wed, 27 Nov 2013 11:17:12 +0100
  • In-reply-to: <CAC3Lx=bqpi2v3cwLZ1bKeWPm262vt+44Ocw1DvQoh1OkGSLQhA@mail.gmail.com>
  • References: <CAC3Lx=bqpi2v3cwLZ1bKeWPm262vt+44Ocw1DvQoh1OkGSLQhA@mail.gmail.com>
The ACSL importer plug-in (used to import external ACSL file) takes care 
of that situation.
Unfortunately, this plugin isn't free.
Without it, your code have to be transformed.

Patrick.

Le 27/11/2013 10:30, David MENTRE wrote:
> At work we have a situation where we want to use C static variables
> (variables visible only to a C file) to hide some internal state of a
> module. However, we have an issue with the assigns clause: as this
> variable is private to the module, it is not visible outside it and
> thus cannot be used in the assigns clause of calling functions. But
> those calling functions needs nonetheless to refer to it, otherwise
> the assigns clause is not proved. How would you handle this properly
> in Frama-C?