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] Collisions using //@ or /*@

  • Subject: [Frama-c-discuss] Collisions using //@ or /*@
  • From: pascal.cuoq at gmail.com (Pascal Cuoq)
  • Date: Fri, 12 Mar 2010 19:09:54 +0100
  • In-reply-to: <21554_1268411287_4B9A6B97_21554_10_1_1268411267.14079.127.camel@ossiriand>
  • References: <OFE86315BC.378D1128-ONC12574E8.00489D32-C12574E8.004964E4@hispano-suiza-sa.com> <20081027155830.4f3518b8@is005115> <0271C9F7-3670-4F21-857E-CB2DCB1F81DB@cea.fr> <21554_1268411287_4B9A6B97_21554_10_1_1268411267.14079.127.camel@ossiriand>
Hello,

> Over a year ago, Jean-Baptiste Jeannin, Virgile and Pascal discussed the
> possibility of using Frama-C on source code annotated with both ACSL and
> doxygen special comments.
>
> Is there a workaround to do so sofar?

The workaround suggested in
http://lists.gforge.inria.fr/pipermail/frama-c-discuss/2009-June/001275.html
should still work with little modifications.

Pascal