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 using user-declared functions in preconditions
- Subject: [Frama-c-discuss] Help with using user-declared functions in preconditions
- From: rod at proteancode.com (Roderick Chapman)
- Date: Fri, 14 Jun 2019 14:46:02 +0100
Dear ACSL experts, Â Perhaps you can help please? In languages like Eiffel, Ada or SPARK, I am used to being able to use user-defined functions in subsequent contracts. Like a Stack ADT, declaring an executable Boolean-valued function called "Empty", then saying "not Empty" in the precondition of my "Pop" function. If I try to do that in ACSL, it fails... the simplest example I can come up with is: int capacity(int x); /*@ requires capacity(x) > 0; Â */ void do_something (const int x); Frama-C (18) says "unbound function capacity" on line 3. This seems like such a common pattern... why doesn't this work? Many thanks, Â Rod Chapman -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20190614/de4c7e30/attachment.html>
- Follow-Ups:
- [Frama-c-discuss] Help with using user-declared functions in preconditions
- From: moy at adacore.com (Yannick Moy)
- [Frama-c-discuss] Help with using user-declared functions in preconditions
- Prev by Date: [Frama-c-discuss] Issue with obfuscated C code
- Next by Date: [Frama-c-discuss] Help with using user-declared functions in preconditions
- Previous by thread: [Frama-c-discuss] Issue with obfuscated C code
- Next by thread: [Frama-c-discuss] Help with using user-declared functions in preconditions
- Index(es):