Re: Why people use "new" & "delete" too much?!!

From:

"Somebody" <somebody@cox.net>

Newsgroups:

comp.lang.c++

Date:

Sat, 5 Jul 2008 13:13:09 -0700

Message-ID:

<uBQbk.16620$%q.8865@newsfe24.lga>

class CFoo
{
};

CFoo* GetFoo()
{
return new CFoo;
}

Still, I agree with you, people over use new and delete. I recently saw a
class library written in C++ that tried to be all C#'ish and required you to
write code like:

classa->InsertItem(new classB(param1));
classa->InsertItem(new classC(param2));

*STUPID*... if your code is too stupid to decide what kind of object should
be created (and keep in mind, I could see doing this for user defined
objects, but these were all internal objects), then why would you expect a
user of your class to?

Plus, that hurts performance.

"Medvedev" <3D.v.World@gmail.com> wrote in message
news:9575b4d8-e4d9-4c0b-a4f8-aefe7864ae33@k30g2000hse.googlegroups.com...

On Jul 5, 11:59 am, red floyd <no.spam.h...@example.com> wrote:

Medvedev wrote:

i see serveral source codes , and i found they almost only use "new"
and "delete" keywords to make they object.
Why should i do that , and as i know the object is going to be destroy
by itself at the end of the app

for example:
class test
{
  public:
       int x;
}

int main(int argc, char **argv)
{
  test *n= new test;
  .
  .
  ...
  delete n;

return 0;
}
i know that the object created this way is in the heap which have much
memory than stack but why they always define objects that way , why
not just say "test n" and the object will be destroyed by itself at
the end of the program! , instead of using "new" and maybe u will
forget to "delete" at the end

Several reasons.

1. They're coming from Java and they don't know any better
2. They're storing polymorphic objects inside containers
3. They need the lifetime of the object to exceed the scope in which
it was declared.

how u can use object after it's scope ends!!