Conflicting class keyword

[kiran kumr]

Hi,

we have the following scenario:

1. A header file that is used in multiple modules a c application and a C++
application.
2. This file has a variable named class[SIZE].
3. How do I declare class now without conflicting with the other variable
class in the common header file.

I cannot rename the variable class and getway without including the header
file.

-Regards,

[Jacek Dziedzic]

kiran kumr wrote:

Hi,

we have the following scenario:

1. A header file that is used in multiple modules a c application and a C++
application.
2. This file has a variable named class[SIZE].
3. How do I declare class now without conflicting with the other variable
class in the common header file.

I cannot rename the variable class and getway without including the header
file.

Perhaps

#undef class
#define class old_class
#include "old_header.h"
#undef class

Does that count as renaming the variable?

I think this should work, although AFAIK it is illegal to re#define
C++ keywords.

HTH,
- J.

[Jim Langston]

"kiran kumr" <ki***************@hp.comwrote in message
news:45******@usenet01.boi.hp.com...

Hi,

we have the following scenario:

1. A header file that is used in multiple modules a c application and a
C++
application.
2. This file has a variable named class[SIZE].
3. How do I declare class now without conflicting with the other variable
class in the common header file.

I cannot rename the variable class and getway without including the
header
file.

-Regards,

If each compiliation unit is to have it's own copy of the variable then make
it static.
static whatever class[SIZE];

If each compiliation unit is to share the one instance of the variable, then
declare it external:
extern whatever class[SIZE];

and in one, and only one, compilation unit (one of the .cpp files) declare
it as a normal global variable:
whatever class[SIZE];

[Colander]

Jim Langston wrote:

"kiran kumr" <ki***************@hp.comwrote in message
news:45******@usenet01.boi.hp.com...

Hi,

we have the following scenario:

1. A header file that is used in multiple modules a c application and a
C++
application.
2. This file has a variable named class[SIZE].
3. How do I declare class now without conflicting with the other variable
class in the common header file.

I cannot rename the variable class and getway without including the
header
file.

-Regards,

If each compiliation unit is to have it's own copy of the variable then make
it static.
static whatever class[SIZE];

If each compiliation unit is to share the one instance of the variable, then
declare it external:
extern whatever class[SIZE];

and in one, and only one, compilation unit (one of the .cpp files) declare
it as a normal global variable:
whatever class[SIZE];

I think you overlooked that in C++ class is an keyword, in C it isn't.

so Legal c code:
int class = 42;
And illegal C++ code:
int class = 42;

Yes there are things that C can do that C++ can't...

[BobR]

Colander wrote in message ...

>Jim Langston wrote:

>If each compiliation unit is to have it's own copy of the variable then

make

>it static.
static whatever class[SIZE];
If each compiliation unit is to share the one instance of the variable,

then

>declare it external:
extern whatever class[SIZE];
and in one, and only one, compilation unit (one of the .cpp files) declare
it as a normal global variable:
whatever class[SIZE];

I think you overlooked that in C++ class is an keyword, in C it isn't.

so Legal c code:
int class = 42;
And illegal C++ code:
int class = 42;

Yes there are things that C can do that C++ can't...

So, in C, this is legal?

int struct = 42;

--
Bob R
POVrookie

[Jim Langston]

"BobR" <Re***********@worldnet.att.netwrote in message
news:0L*********************@bgtnsc04-news.ops.worldnet.att.net...

>
Colander wrote in message ...

>>Jim Langston wrote:

>>If each compiliation unit is to have it's own copy of the variable then

make

>>it static.
static whatever class[SIZE];
If each compiliation unit is to share the one instance of the variable,

then

>>declare it external:
extern whatever class[SIZE];
and in one, and only one, compilation unit (one of the .cpp files)
declare
it as a normal global variable:
whatever class[SIZE];

I think you overlooked that in C++ class is an keyword, in C it isn't.

so Legal c code:
int class = 42;
And illegal C++ code:
int class = 42;

Yes there are things that C can do that C++ can't...

So, in C, this is legal?

int struct = 42;

You're absolutely right, I just typed in the OP's variable name on auto
pilot. Yeah, can't use any keyword as a var name (including struct).

So, no, int struct = 42; is not legal in c++