Need Help with static struct class definition

[SteveM]

This is probably an easy answer but since I am fairly new to C++ for
some reason I can't see it :-( Any help would be appreciated
:-)

I have a class:

class AClass
{
public:

[Victor Bazarov]

SteveM wrote:

This is probably an easy answer but since I am fairly new to C++ for
some reason I can't see it :-( Any help would be appreciated
:-)

I have a class:

class AClass
{
public:
.
. (some functions)
private:
struct PData
{
static int aValue;
static int bValue;
}
Missing a semicolon here
}
And here

I am clueless as to how to format the definition.
What do you mean by "format the definition"?
Everything I have
tried up till now has been flagged by the compiler
Flagged how?
Please Help

BTW What I am needing to do is make the variables of the struct
available to static functions (in public of this class).
Aren't they? Since PData is a member, it should be available, and since
its members are public (by default), they should be available as well.
if I need to
make the struct static also or just need the struct static but not the
members I really dont care. The ultimate goal here is to 1.) get
something to work 2.) Get a better understanding of how C++ does things
(such as static structs or static members of structs)

Read FAQ 5.8.

V

[Jay Nabonne]

On Fri, 23 Sep 2005 09:20:58 -0700, SteveM wrote:

This is probably an easy answer but since I am fairly new to C++ for
some reason I can't see it :-( Any help would be appreciated
:-)

I have a class:

class AClass
{
public:
.
. (some functions)
private:
struct PData
{
static int aValue;
static int bValue;
}
}

I am clueless as to how to format the definition. Everything I have
tried up till now has been flagged by the compiler
Please Help

In a CPP file:

int AClass::PData::aValue;
int AClass::PData::bValue;

You can also initialize them:

int AClass::PData::aValue = 42;
int AClass::PData::bValue = 314;

- Jay

[SteveM]

Thanks Jay,

That is exactly what I was needing :-)

Also sorry to Victor for the unclear way in which I presented my
problem :-(
I will try to be more clear in the future. I did miss some things in my
attempt at
explaining the problem. sorry

-Steve :-)