DaniWeb Forum Index > Software Development > C++

Is there a way to prevent creating objects on heap?

Please support our C++ advertiser: Intel Parallel Studio Home

Thread Solved

•

Join Date: Oct 2007

Posts: 15

Reputation: jaux is an unknown quantity at this point

Solved Threads: 2

jaux

Offline

Newbie Poster

Is there a way to prevent creating objects on heap?

Dec 12th, 2007

Yesterday I saw a question that was asking to prevent creating objects on heap.

After some thoughts, I came out the following:

 Help with Code Tags 
 C++ Syntax (Toggle Plain Text) 
class Foo
{
public:
    Foo(const Foo& f) {}
    static Foo getAnInstance()
    {
        return Foo();
    }
private:
    Foo() {}
};
class Foo
{
public:
    Foo(const Foo& f) {}
    static Foo getAnInstance()
    {
        return Foo();
    }
private:
    Foo() {}
};

But this can only guarantee the first object is on stack and it can’t go further because there is a public copy ctor.

I haven't seen the point of the question, but it's fun to think about; so my question: Is there a way to do so?

•

Join Date: Aug 2005

Posts: 15,578

Reputation: Ancient Dragon has a reputation beyond repute

Solved Threads: 1486

Ancient Dragon Ancient Dragon is offline

Offline

Still Learning

Re: Is there a way to prevent creating objects on heap?

Dec 12th, 2007

methods of a class are never ever on the stack -- only data objects go there.

 Help with Code Tags 
 C++ Syntax (Toggle Plain Text) 
int main()
{
    Foo f; // object f goes on the stack, but not the methods of that object.
}
int main()
{
    Foo f; // object f goes on the stack, but not the methods of that object.
}

Don't PM me with questions -- you might get a nasty PM in response. If you have a question then post it in one of the forums.

•

Join Date: Oct 2007

Posts: 15

Reputation: jaux is an unknown quantity at this point

Solved Threads: 2

jaux

Offline

Newbie Poster

Re: Is there a way to prevent creating objects on heap?

Dec 12th, 2007

Thank you, Dragon. Does that mean that, on our side (not the client side), to restrict the location of object creation is pointless? I mean that it's client's responsibility to determine where his/her objects should be located.

Last edited by jaux; Dec 12th, 2007 at 9:07 pm. Reason: clarification

•

Join Date: Dec 2006

Posts: 1,089

Reputation: vijayan121 is a name known to all

Solved Threads: 164

vijayan121 vijayan121 is offline

Offline

Veteran Poster

Re: Is there a way to prevent creating objects on heap?

Dec 12th, 2007

see: More Effective C++: 35 More Ways to Improve Your Programs and Designs (Scott Meyers)
ITEM 27. Requiring or Prohibiting Heap-Based Objects.
and http://www.aristeia.com/BookErrata/M...ts_frames.html