Re: "static" question
From: Alf P. Steinbach (alfps_at_start.no)
Date: 04/18/04
- Next message: Steven T. Hatton: "Re: Would a static_cast be better style here?"
- Previous message: Pat: ""static" question"
- In reply to: Pat: ""static" question"
- Next in thread: Pat: "Re: "static" question"
- Reply: Pat: "Re: "static" question"
- Reply: Fraser Ross: "Re: "static" question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 18 Apr 2004 14:04:51 GMT
* "Pat" <Pat@Pat.com> schriebt:
> I would like to know what is the meaning of :
>
> static vector<int> v;
>
> What is the difference with:
>
> vector<int> v;
>
That depends on the context of the declaration.
If it is at namespace scope (outside any function or class) then 'static'
means that v has internal linkage, i.e., in practical terms, is not visible to
the linker outside the compilation unit.
If it is in a class or function then 'static' means that v has global
lifetime; for a class it is a single variable instead of a member variable in
each instance of the class; for a function it is a single variable instead of
an automatic variable created & destroyed for each call of the function.
-- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
- Next message: Steven T. Hatton: "Re: Would a static_cast be better style here?"
- Previous message: Pat: ""static" question"
- In reply to: Pat: ""static" question"
- Next in thread: Pat: "Re: "static" question"
- Reply: Pat: "Re: "static" question"
- Reply: Fraser Ross: "Re: "static" question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|