Constructor with 'new'...

Hi all,
I would have a question:
When I want to construct an object (with some parameter, e.g. string) in a normal way, I use:

Code:

SimpleClass simpleObject("ObjectID");

When I want to construct multiple objects without parameters in "dynamic" way (for example, 4 objects), I use:

Code:

SimpleClass* pSimpleObject = new SimpleClass[4];

But what is the code, when I would like to construct multiple objects in dynamic way "WITH" some parameters?

Code:

SimpleClass* pSimpleObject = ??? // new SimpleClass("ObjectID")[4], or what?

Thanks.

Petike

Not possible, at least at the moment. You can simulate it with placement new, but that can be ugly and error prone, so it would be much simpler to just pick a container like std::vector and do:

Code:

std::vector<SimpleClass> simpleObjects(4, SimpleClass("ObjectID"));

The placement new trick would be done under the hood, plus you get the benefit of not having to do manual memory management.

I've always wondered why they didn't put in support for that too. Seems like a common enough thing to want to do.
Any plans to allow it in the next standard?

Any plans to allow it in the next standard?

According to this article, the answer is yes.

The real question will be when will the full support for C++0x be enforced by your compiler.

The real question will be when will the full support for C++0x be enforced by your compiler.

I am not sure if any compiler has full support for C++03, so the answer might well be "never".

But change it to "reasonable", and the answer is somewhere between 2010 and 2013.

Originally Posted by laserlight

plus you get the benefit of not having to do manual memory management.

ah yes, 'benefit', snicker....

There is a major product out on release right now that is essentially still born because they took advantage of this 'benefit'. Now they have memory leaks that they cant track down. While this can have advantages, its not a magic bullet solution to memory management.

There is a major product out on release right now that is essentially still born because they took advantage of this 'benefit'. Now they have memory leaks that they cant track down. While this can have advantages, its not a magic bullet solution to memory management.

Stroustrup notes the possible use of garbage collection for "litter collection" in such a case (but again GC is not a magic bullet solution for memory management either). I reason that the project in question did not "systematically and correctly" use "RAII plus smart pointers".