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: david.delmas at airbus.com (David Delmas)
  • Date: Fri, 12 Mar 2010 17:27:47 +0100
  • In-reply-to: <0271C9F7-3670-4F21-857E-CB2DCB1F81DB@cea.fr>
  • References: <OFE86315BC.378D1128-ONC12574E8.00489D32-C12574E8.004964E4@hispano-suiza-sa.com> <20081027155830.4f3518b8@is005115> <0271C9F7-3670-4F21-857E-CB2DCB1F81DB@cea.fr>
Dear all,

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?

Thank you for your advice,
--
David

Le lundi 27 octobre 2008 ? 16:32 +0100, Pascal Cuoq a ?crit :
> >
> >> Some JavaDoc-like documentation tools can badly interfere with  
> >> Frama-C by
> >> also requiring special comments beginning by /*@ or //@. For  
> >> example, the
> >> Do you have any idea of how to go around this problem? Are the /*@  
> >> and //@
> >> syntaxes, which were already used by JML, supposed to somehow be
> >
> > In the current version of Frama-C (and in the forthcoming release),  
> > the
> > only way to overcome this issue is to disable annotation processing
> > entirely (with the -no-annot option). The '@' sign was indeed chosen  
> > to
> > introduce ACSL annotation because it was already used by JML (while
> > javadoc and doxygen use '*' for structured documentation).
> 
> However, I should add that the expected character for ACSL annotations  
> is
> not hardwired anywhere in Frama-C.
> It will be relatively easy to introduce a command-line
> option to change this character for compatibility with other  
> annotation tools
> in the future.
> 
> 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
> 
> This mail has originated outside your organization, either from an external partner or the Global Internet.
> Keep this in mind if you answer this message.
> 
> 

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.