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

 
 

You are not allowed to post comments on this tracker with your current authentication level.

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

Submitted by:  Sašo Kiselkov <diablos>
Submitted on:  Sat 11 Mar 2006 09:28:57 AM UTC  
 
Category: Base/FoundationSeverity: 3 - Normal
Item Group: Change RequestStatus: Fixed
Privacy: PublicAssigned to: None
Open/Closed: Closed

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>
Project 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>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Sat 11 Mar 2006 11:42:07 AM UTCCaSStatusNone=>Fixed
  Open/ClosedOpen=>Closed

Back to the top


Powered by Savane 3.1-cleanup1