bugGNUstep - Bugs: bug #16062, Avoid using "class" and...

Group
 
 

bug #16062: Avoid using "class" and other C++ keywords in macros

Submitter:  Sašo Kiselkov <diablos>
Submitted:  Sat 11 Mar 2006 09:28:57 AM UTC
   
 
Category:  Base/Foundation Severity:  3 - Normal
Item Group:  Change Request Status:  Fixed
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 11 Mar 2006 11:42:07 AM UTC, comment #1: 

I changed the header and marked this as 'fixed' ... though I believe the problem is imaginary so it doesn't really count as a fix.  Certainly 'class' is a reserved word, but that doesn't mean you can't have it as a preprocessor macro argument.  It was worth changing for the sake of avoiding confuion for C++ programmers though.

Richard Frith-Macdonald <CaS>
Group Member
Sat 11 Mar 2006 09:28:57 AM UTC, original submission:  

I found that in NSInvocation.h the word "class" is used in a macro argument. I'd suggest to replace it with "aClass" or anything else instead (and not only in NSInvocation.h, but in all GNUstep headers), as it might create weird problems when GNUstep is used from Objective-C++ code, since GCC now has ObjC++ support.

Sašo Kiselkov <diablos>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 2 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-03-11 CaS StatusNone Fixed
    Open/ClosedOpen Closed

Back to the top

Powered by Savane 3.13-02a9.
Corresponding source code