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] linked lists?
- Subject: [Frama-c-discuss] linked lists?
- From: virgile.prevosto at cea.fr (Virgile Prevosto)
- Date: Thu, 01 Dec 2011 09:14:10 +0100
- In-reply-to: <A462DFA8-0824-4A6B-AB64-56FF1F9861FA@udel.edu>
- References: <A462DFA8-0824-4A6B-AB64-56FF1F9861FA@udel.edu>
Hello, On 30/11/2011 20:42, Stephen Siegel wrote: > Hi, I was trying to do something with this example taken from one of > the ACSL manuals, but got an unimplemented feature error. I'm still > using Carbon release. > /*@ > requires reachable(p,\null); > assigns { q->hd | struct list *q ; reachable(p,q) } ; > @*/ I havn't looked at it in very detail, but it is most probably the assigns clause that's causing trouble here. Comprehension (i.e. the possibility of considering the set of all q->hd such that reachable(p,q) is supported by the front-end, but not by any plug-in I know of. I'm afraid Frama-C Nitrogen won't help in this particular case. There have been few attempts to study such structures so far, but I have to admit that it is not the main topic of most usages of Frama-C. Best regards, -- E tutto per oggi, a la prossima volta Virgile
- Prev by Date: [Frama-c-discuss] using floating-point + in spec
- Next by Date: [Frama-c-discuss] Some question concerning code transformation using Cil and Frama_c_visitors.
- Previous by thread: [Frama-c-discuss] using floating-point + in spec
- Next by thread: [Frama-c-discuss] linked lists?
- Index(es):