--- layout: fc_discuss_archives title: Message 56 from Frama-C-discuss on July 2010 ---
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] how to deal with malloc in frama-c (boron)



It would be great if the examples in examples-c were updated for jessie. It
might cut down on a lot of
questions about how to annotate  programs.  For instance, the parray.c code
is just the sort of thing
that the jessie/ACSL tutorials don't seem to show and I'm not sure where to
look other than these examples,
which aren't correct so they don't really help.


-A

>
> > In addition, we try and look at the examples available in
> > the directory examples-c, especially puf/ but we did not
> > figure out how to compile these examples.
>
> The files in puf/ are Caduceus examples, not Jessie examples. Oh, and
> they also specify allocation functions with assigns \nothing. So if my
> colleagues have an explanation of why it's not wrong to use that
> clause in ACSL for a function that obviously has internal
> side-effects, I would be eager to hear it.
>
> I would also welcome an explanation of what "\forall ref *p;" means in
> ACSL and if it is still allowed (in ACSL) to use it in the same way it
> is used in puf/parray.c.
>
> Pascal
>
> _______________________________________________
> Frama-c-discuss mailing list
> Frama-c-discuss at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/frama-c-discuss
>



-- 
Alwyn E. Goodloe, Ph.D.
agoodloe at gmail.com

Computer Scientist
National Institute of Aerospace
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20100730/5f0f5510/attachment.htm>