opensubscriber
   Find in this group all groups
 
Unknown more information…

d : dotnet-rotor@discuss.develop.com 25 March 2006 • 4:01PM -0500

[DOTNET-ROTOR] Contract analysis tool [Rotor 2.0 released
by Alexander Petrossian (PAF)

REPLY TO AUTHOR
 
REPLY TO GROUP




Jan,
I see that you guys introduced contract checking with some external contract
analysis tool:
lots of
        LEAF_CONTRACT
everywhere.

a breaf look at sources shows that that macro boils down to still
undocumented __annotation feature, which, judging from staticcontract.h
comments [below] is a way to store some info to .pdb files.

the question is...
is that analysis tool somewhere publicly available? [maybe I just missed
something]

in case it is not, I'm sure there is somewhere some information just about
the idea itself.
if you have couple of links on the subject handly, they would be extremely
welcome.

learning and admiring,

Alexander Petrossian, Moscow, Russia


// PDB annotations for the static contract analysis tool. These are
seperated
// from Contract.h to allow their inclusion in any part of the system.
//
#ifdef _X86_
//
// currently, only x86 has a static contract analysis tool, so let's not
// bloat the PDBs of all the other architectures too..
//
...
#define ANNOTATION_FN_LEAF                  __annotation(L"LEAF "
SCAN_WIDEN(__FUNCTION__))


> -----Original Message-----
> From: Discussion of the Rotor Shared Source CLI
> implementation [mailto:DOTNET-ROTOR@DISC...] On
> Behalf Of Jan Kotas
> Sent: Friday, March 24, 2006 5:16 PM
> To: DOTNET-ROTOR@DISC...
> Subject: [DOTNET-ROTOR] Rotor 2.0 released
>
> On behalf of the entire Rotor team, I am pleased to announce the 2.0
> release of Rotor.

===================================
This list is hosted by DevelopMentorĀ®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.