memset 'this' in constructor?

[hack_tick]

hi Guys!

I am having a class, having around 300+ pointers ONLY, I need to set
them all NULL, when the object is created.

The best way I think is

memset(this, NULL, sizeof(classnam e));

whats your suggestion??
Will this break anything?? as it is done in constructor??

any suggestions???

[hack_tick]

Also guys what do you all suggest about deleting?? as this class is
only going to have Pointers as member variable,
hack_tick wrote:

hi Guys!

I am having a class, having around 300+ pointers ONLY, I need to set
them all NULL, when the object is created.

The best way I think is

memset(this, NULL, sizeof(classnam e));

whats your suggestion??
Will this break anything?? as it is done in constructor??

any suggestions???

[kkk]

hack_tick wrote:

hi Guys!

I am having a class, having around 300+ pointers ONLY, I need to set
them all NULL, when the object is created.

The best way I think is

memset(this, NULL, sizeof(classnam e)); This will turn the virtual fn pointer of your object to NULL.

whats your suggestion??
Will this break anything?? as it is done in constructor??

any suggestions???

[Prawit Chaivong]

hack_tick wrote:

hi Guys!

I am having a class, having around 300+ pointers ONLY, I need to set
them all NULL, when the object is created.

The best way I think is

memset(this, NULL, sizeof(classnam e));

whats your suggestion??
Will this break anything?? as it is done in constructor??

any suggestions???

You have at least two things to be concern.
1. Have you derived this class from anyclass?
If yes, but you might say that there isn't any data member in Base
class (please read 2)
2. Is there any virtual method inside this class?

[Noah Roberts]

hack_tick wrote:

hi Guys!

I am having a class, having around 300+ pointers ONLY, I need to set
them all NULL, when the object is created.

The best way I think is

memset(this, NULL, sizeof(classnam e));

whats your suggestion??
Will this break anything?? as it is done in constructor??

any suggestions???

Sounds like you got a blob on your hands. Factor it and make it more
maintainable. When you think, "I would like to memset because this
thing has too many damn variables," it is time to rethink your design.

[hack_tick]

hi
Prawit Chaivong wrote:
[....]

You have at least two things to be concern.
1. Have you derived this class from anyclass?
If yes, but you might say that there isn't any data member in Base
class (please read 2)
nope!!
2. Is there any virtual method inside this class?

nope

The class is not meant to be derived, it is just meant to handle all
those global variables into one namespace with heap control, so whats
your suggestion??

[hack_tick]

hi,

Noah Roberts wrote:
[...]

Sounds like you got a blob on your hands. Factor it and make it more
maintainable. When you think, "I would like to memset because this
thing has too many damn variables," it is time to rethink your design.

Actually I am porting existing app, to Symbian, which require me to
move all the global variables to Thread Local Storage (TLS), by making
them member to a class, as Symbian does not support Global Variables,
on some of the OS versions.

[Old Wolf]

hack_tick wrote:

I am having a class, having around 300+ pointers ONLY, I need to set
them all NULL, when the object is created.

The best way I think is

memset(this, NULL, sizeof(classnam e));

1) won't set pointers to NULL (will set them to all bits zero, which
might be different)

2) might roach other parts of your object (eg. a vtable).

If your question is "does this work in MSVC on windows XP"
then ask in some other newsgroup.

To initialize them properly then you should store all your pointers
in a container that will initialize all of its members, eg:

struct Foo
{
std::vector<T *> pointers;
Foo(): pointers(300, 0) {}
}

You could use a map<string, T *> if you want to refer to them by name.

[Alf P. Steinbach]

* hack_tick:

hi,

Noah Roberts wrote:
[...]

Sounds like you got a blob on your hands. Factor it and make it more
maintainable. When you think, "I would like to memset because this
thing has too many damn variables," it is time to rethink your design.

Actually I am porting existing app, to Symbian, which require me to
move all the global variables to Thread Local Storage (TLS), by making
them member to a class, as Symbian does not support Global Variables,
on some of the OS versions.

/One/ global variable is one too many.

And you have 300...

Anyways, default initialization (or per C++2003, value initialization)
will do the trick.

struct PODPointers
{
void* myGlobalPointer 1;
void* myGlobalPointer 2;
};

struct Pointers: PODPointers
{
Pointers(): PODPointers() {}
};

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Steve Pope]

hack_tick <sh************ @gmail.com> wrote:

The class is not meant to be derived, it is just meant to handle all
those global variables into one namespace with heap control, so whats
your suggestion??

What do you mean by "with heap control"?

If they are just a bunch of global variables, and you are
not creating multiple objects of this class, consider just
making them variables in a namespace and don't use a class.
Then they can be initialized statically, which cost nothing
in runtime.

Steve