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] Help with -wp-init-const and static evaluation of constants

  • Subject: [Frama-c-discuss] Help with -wp-init-const and static evaluation of constants
  • From: rod at proteancode.com (Roderick Chapman)
  • Date: Thu, 18 Jul 2019 09:59:18 +0100
  • In-reply-to: <CA+yPOVjhCvkoyLc1y1y+35cPX-e_P=-4pqyG8FQb=cxp9zZS8w@mail.gmail.com>
  • References: <c5309feb-8597-c141-6dd2-48da2b49e048@proteancode.com> <CA+yPOVjhCvkoyLc1y1y+35cPX-e_P=-4pqyG8FQb=cxp9zZS8w@mail.gmail.com>
On 18/07/2019 07:14, Virgile Prevosto wrote:
> //@ assert c1 == 300;
>
> at the beginning of the function and everything gets proved.

That seems to work, but is unacceptable - the whole point of having 
named constants (especially a set of them where the values depend on 
each other) is to avoid having literal "magic numbers" all over the place.

  - Rod


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20190718/4cc8b637/attachment.html>