What does line 162 do ?

[Rafael Anschau]

159: static PartsList GlobalPartsList;
160: };
161:
162: PartsList PartsList::GlobalPartsList;

I would understand if it initialized the object
GlobalPartsList with some value, but as it is now, it seems to me
without purpose.

Thanks,

Rafael

[Victor Bazarov]

Rafael Anschau wrote:

159: static PartsList GlobalPartsList;
160: };
161:
162: PartsList PartsList::GlobalPartsList;

I would understand if it initialized the object
GlobalPartsList with some value, but as it is now, it seems to me
without purpose.

It _defines_ the static data member. Read up on static data members.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

[Rafael Anschau]

Yes, my text says it initializes or defines it there. That line 159
only declares it.
But initializes it, defines it with what ? What it does is to make it
possible to later assign
a value ?

[]´s

Rafael

On May 9, 12:26 pm, "Victor Bazarov" <[e-mail]:

Rafael Anschau wrote:

159: static PartsList GlobalPartsList;
160: };
161:
162: PartsList PartsList::GlobalPartsList;

I would understand if it initialized the object
GlobalPartsList with some value, but as it is now, it seems to me
without purpose.

It _defines_ the static data member. Read up on static data members.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

[Jim Langston]

On May 9, 12:26 pm, "Victor Bazarov" <[e-mail]:

>Rafael Anschau wrote:

>>159: static PartsList GlobalPartsList;
160: };
161:
162: PartsList PartsList::GlobalPartsList;

>>I would understand if it initialized the object
GlobalPartsList with some value, but as it is now, it seems to me
without purpose.

It _defines_ the static data member. Read up on static data members.

Rafael Anschau wrote:

Yes, my text says it initializes or defines it there. That line 159
only declares it.
But initializes it, defines it with what ? What it does is to make it
possible to later assign
a value ?

[]´s

Please do not top post. Message rearranged.

Since GlobalPartsList is static, there can be only one in the program.
There can be only one definition.

Line 162 is simply *the* definition. Line 159 is the declaration. You can
not define a static variable inside a class declaration, you can only
declare it. So outside the class declaration you need the definition, which
you have.

It may make more sense if it was an int.

class foo
{
static int bar;
};

int foo::bar = 42;

Your PartsList PartsList::GlobalPartsList; is doing the same thing, it is
just default constructed.
--
Jim Langston
ta*******@rocketmail.com

[Rafael Anschau]

Thanks, but same question.

int foo::bar = 42;//OK, =42
int foo::bar; //??

[]´s

Rafael

[Rafael Anschau]

Thanks but same question:

int foo::bar = 42; //Ok, =42
int foo::bar;// ?? =??

[]´s

Rafael

[Victor Bazarov]

Rafael Anschau wrote:

Thanks, but same question.

int foo::bar = 42;//OK, =42
int foo::bar; //??

If your question is what value 'foo::bar' gets, the answer is 0.

[]´s

Sorry, I for one don't understand. "Brackets's"?

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

[Martin York]

On May 9, 8:43 am, Rafael Anschau <[e-mail]:

Yes, my text says it initializes or defines it there. That line 159
only declares it.
But initializes it, defines it with what ? What it does is to make it
possible to later assign
a value ?

When an object is initialised it calls the objects constructor.
So line 162 creates the object and calls the objects constructor (see
constructor for PartsList). Once it has been constructed you can now
call all the public methods available in PartsList.
PartsList::GlobalPartsList.doSomthing()

[Rafael Anschau]

Thank you now I get it. The purpose is to make members avalible
and run the constructor. Great.

[]´s

Rafael

[Rafael Anschau]

>Sorry, I for one don't understand. "Brackets's"?

That´s an old 80´s 90´s (70´s ?) electronic compliment.

[]´s

Rafael

[James Kanze]

On 9 mai, 20:09, Rafael Anschau <[e-mail]:

Thank you now I get it. The purpose is to make members
avalible and run the constructor.

Or not. Even if the object doesn't have a constructor, you need
a definition. Very basically, it's the definition which
allocates the memory for the object (or causes the
compiler/linker to allocate it).

--
James Kanze (GABI Software) email:ja*********@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]

[Rolf Magnus]

Rafael Anschau wrote:

>>Sorry, I for one don't understand. "Brackets's"?

That´s an old 80´s 90´s (70´s ?) electronic compliment.

[]´s

But it's probably supposed to use the apostrohpe (') and not the
french "accent aigu" over an empty space (´).

[Rolf Magnus]

Rafael Anschau wrote:

Thank you now I get it. The purpose is to make members avalible
and run the constructor. Great.

No, it isn't. Think of the declaration as an entry in the table of contents
in a book. It tells you which chapters exist and how to find them, but it
doesn't contain the actual chapter text. So you need to add the chapter
content somwehere to your book, just like you need to define the static
member variable somewhere, since otherwise, the TOC entry leads to nowhere.

[Rolf Magnus]

Rafael Anschau wrote:

>>Sorry, I for one don't understand. "Brackets's"?

That´s an old 80´s 90´s (70´s ?) electronic compliment.

[]´s

But it's probably supposed to be using an apostrophe and not an acute accent
over an empty space.