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] Jessie - behavior-specific loop invariants
- Subject: [Frama-c-discuss] Jessie - behavior-specific loop invariants
- From: virgile.prevosto at cea.fr (Virgile Prevosto)
- Date: Mon, 8 Nov 2010 14:44:33 +0100
- In-reply-to: <42050C88D59E144CA358159FF0E6018B09067A@TITAN.first.fraunhofer.de>
- References: <42050C88D59E144CA358159FF0E6018B09067A@TITAN.first.fraunhofer.de>
Hello Kerstin, Le lun. 08 nov. 2010 13:59:08 CET, "Kerstin Hartig" <kerstin.hartig at first.fraunhofer.de> a ?crit : > As we usually divide spec. and impl. I experienced the following problem: > Including the specification file to the implementation file results in some > unknown behavior error. > > Is this a bug? Or is there something I overlooked? > This is a bug. In fact, it is fixed in the current development version and Frama-C Carbon will behave as you expect. Best regards, -- E tutto per oggi, a la prossima volta. Virgile
- References:
- [Frama-c-discuss] Jessie - behavior-specific loop invariants
- From: kerstin.hartig at first.fraunhofer.de (Kerstin Hartig)
- [Frama-c-discuss] Jessie - behavior-specific loop invariants
- Prev by Date: [Frama-c-discuss] Jessie - behavior-specific loop invariants
- Next by Date: [Frama-c-discuss] beginners problem - pointer swap example
- Previous by thread: [Frama-c-discuss] Jessie - behavior-specific loop invariants
- Next by thread: [Frama-c-discuss] beginners problem - pointer swap example
- Index(es):