Re: [sca-c-cpp] NEW ISSUE: Use #pragms for C/C++ Annotations.

[Bryan Aupperle <aupperle@us.ibm.com>]

This issue has been assigned id CCPP-49
in the Jira system. 
See http://www.osoa.org/jira/browse/CCPP-49

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
Master Inventor

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

"David Haney" <haney@roguewave.com>

08/22/2008 11:43 AM

To	<sca-c-cpp@lists.oasis-open.org>
cc
Subject	[sca-c-cpp] NEW ISSUE: Use #pragms for C/C++ Annotations.

Target: C & C++ C&I Specifications 

Description: Use #pragma for C/C++ Annotations

The current specification uses annotations embedded in comments in order
to provide additional information about methods and arguments.  The
C/C++ languages also provide a #pragma preprocessor directive that
allows specifying additional information to a compiler about the code.
Instead of using comments for SCA annotations, we could instead use
#pragmas.

Pros:
                
- Follows convention of other C/C++ extensions (like OpenMP).
                
- Allows rudimentary namespacing of directives

Cons:
                
- Some compilers will ignore when unrecognized pragmas are
present.   
        Users will need to disable those warnings.
 (They are required
by 
        The standard to not fail on unrecognized pragams).

Proposal:

The simplest implementation would involve replacing the existing
convention of:

// @WebService(name="op1")

With something like:

#pragma sca WebService(name="op1")

We could also investigate changing the format, I'm not sure if that
would be necessary or what that should look like.


-- David Haney
-- Director of Architecture
-- Rogue Wave Software
-- http://www.roguewave.com/



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php