Initialize static members outside the class

>The question is how to define these initialise. *You know, for a
simple member, I can
do something like:
* *int MyClass::myMember = 123;
but for complicated non-POD types, such as a std::vector, how do I
initialize it by
push_back() many elements into it? * You see my problem? *Thanks.

On Jul 15, 5:40 pm, Lionel B <m...@privacy.netwrote:>
The question is how to define these initialise. You know, for a simple
member, I can
do something like:
int MyClass::myMember = 123;
but for complicated non-POD types, such as a std::vector, how do I
initialize it by
push_back() many elements into it? You see my problem? Thanks.

We must did the
following work in C for many many times:
>
// file: foo.c
>
static const int my_magic_code_table [] {
1,
9,
103,
2,
...
};
>
Now I sure you see what I was looking for is just a equivalent of above
in C++ as simple as we can approach.

On Tue, 15 Jul 2008 06:54:33 -0700, Steven Woody wrote:>>>>
Doh! Why didn't you just say that in the first place?
>
// foo.hpp:
>
class Foo
{
private:
static const int my_magic_code_table[];
public:
static const std::vector<intmy_magic_code_vector;
>
};
>
// foo.cpp:
>
const int Foo::my_magic_code_table[] =
{
1,
9,
103,
2
>
};
>
const std::vector<intFoo::my_magic_code_vector(
Foo::my_magic_code_table,
Foo::my_magic_code_table + sizeof(Foo::my_magic_code_table)/sizeof(int)
);
>
Although I'm not sure why you'd want a vector at all here

Steven Woody a écrit :

There is still boost.assign:http://www.boost.org/doc/libs/1_35_0...doc/index.html

If I understand correctly (I have never used it), this will give
something like:

const std::vector<intmagic_code=list_of(1)(9)(103)(2)... (42);

James Kanze a écrit :
>>>>>>
The strcpy(), strcat, str... were designed for chaining but AFAIK, it is
rarely used that way. I guess it would also be marginally useful for
std::vector<>.
>
>
>>
That's hideous. :)
>
--
Michael

On 16 Lug, 13:02, Michael DOUBEZ <michael.dou...@free.frwrote:
>
>
>
>
>>>>>>>>>>>
Hi to all,
I use the following template to trigger static member functions (that
can be used to do any type of initalization ).
It always seemed to work in the few cases I've used it. The only doubt
is the constructor of the template, that refers to the static member
object to enforce instantiation. My doubt is that some compiler
optimization might throw that away. With gcc it never seems to happen
with any optimization.
Any comment?
Regards to all,
Francesco
>
#include <iostream>
#include <vector>
>
template< typename T >
class CAutoInitializer
{
protected:
* * // enforce sInit instantiation
* * CAutoInitializer() { return; sInit; }
private:
* * struct CInit { CInit() { T::StaticInitializer(); } };
* * static CInit sInit;
>
};
>
template< typename T >
typename CAutoInitializer< T >::CInit CAutoInitializer< T >::sInit;
>
//
>
class CSomething : CAutoInitializer< CSomething >
{
public:
* * // avoid static init fiasco
* * static std::vector< int & GetVec()
* * { static std::vector< int sVec; return sVec; }
>
* * static void StaticInitializer()
* * {
* * * * std::cout << "Do anything you want here\n";
* * * * GetVec().push_back( 10 );
* * }
>
};
>
//
>
class CSomethingElse : CAutoInitializer< CSomethingElse >
{
public:
* * static void StaticInitializer()
* * { *std::cout << "Do something else here\n"; }
>
};
>
int main()
{
* * std::cout << "main\n";
* * CSomething * * *obj1;
* * CSomethingElse *obj2;
* * std::cin.get();
>
>
>
}- Nascondi testo citato
>
- Mostra testo citato- Nascondi testo citato
>
- Mostra testo citato

>::CInit

>::sInit;

James Kanze a écrit :

The strcpy(), strcat, str... were designed for chaining but
AFAIK, it is rarely used that way.

I guess it would also be marginally useful for std::vector<>.

That's hideous. :)

On Jul 15, 3:54 pm, Steven Woody <narkewo...@gmail.comwrote:
>>
[...]
>>
But what is the specific data? If it's known at compile time
(or even if it's not---"something" can be an istream_iterator),
you can use the second. And if you don't know it until after
entering main, you can't make the vector const.
>>
Well, I've yet to find a case where the template constructor
taking two iterators wouldn't work (and the data was known
before hand, of course). And you can always use something like:
>
std::vector< int const Class::staticVector(
someFunctionReturningAVectorOfInt() ) ;
>