How to avoid object creation in heap/stack

[gpraghuram]

HI All,
Someone asked me the following question and i am not able to get an answer for this.
In c++ how will you restrict
1)object creation in heap
2)object creation in stack

Can anyoine throw some light into this

Raghuram

[ruskalym]

Hello,

To create an object in heap, you can allocate it through `new` keyword.

To create an object in stack, you can define it as a local variable, in a function or a method.

[JosAH]

HI All,
Someone asked me the following question and i am not able to get an answer for this.
In c++ how will you restrict
1)object creation in heap
2)object creation in stack

Can anyoine throw some light into this

Raghuram

Ruskalym (see above) already answered your question: if you don't want users
to be able to create objects on the heap, overload the new operator such that
it throws an error (or make it a private operator so that the user can't access it).

If you don't want objects on the stack you could make all constructors private
and add a 'factory method' that builds objects on the heap for the user.

kind regards,

Jos

[gpraghuram]

Ruskalym (see above) already answered your question: if you don't want users
to be able to create objects on the heap, overload the new operator such that
it throws an error (or make it a private operator so that the user can't access it).

If you don't want objects on the stack you could make all constructors private
and add a 'factory method' that builds objects on the heap for the user.

kind regards,

Jos

Thanks a lot Jos....
I got the answer.
How can you make new operator private?
Did u mean that overloading shuld be made private?

Raghuram

[JosAH]

Thanks a lot Jos....
I got the answer.
How can you make new operator private?

Erm, you can't; I goofed (I had some strange sort of Java code in my head when
I wrote that (incorrect) remark). It is possible to supply your own implementation
for the global operator new() though; I think that's the way to go if you don't want
any objects on the heap.

Sorry for the mistake and

kind regards,

Jos

[duedony]

Dear Jos:

>>It is possible to supply your own implementation
>>for the global operator new() though;

If I can implement the global operator new(), I can calculate the total heap usage for C++ object creation on my system.

[abnsreddy]

In c++ how will you restrict
1)object creation in heap
>>
make private the following functions:
void *operator new(size_t),
void *operator new[](size_t)
2)object creation in stack
>>
make constructor and destructor private
have seperate static functions like create and destroy functions which will internally call constructor and destructor respectively