Question about initializing an object without assigning...

[Zingam]

int main(...) {
     .....
     Application app(argc, argv);
     new ApplicationUI(&app);
     .....
}

int main(...) {
     .....
     Application app(argc, argv);
     new ApplicationUI(&app);
     .....
}

To copy to clipboard, switch view to plain text mode 

I have seen a code like the above a few times but I don't understand why is it valid. Where does the initalized object go?

[wysota]

It doesn't "go" anywhere, it is on a heap like any other object allocated with "new", it is just not assigned to any public variable.

[Zingam]

And what would be a good use case for initializing an object that I cannot access through I variable?
I'd like to fill this hole in my C++ knowledge but I cannot figure it out yet.

[wysota]

C++ has nothing to do with this. You don't need to assign the return value of new to be able to use the object. For instance the object might "install" itself on some other object in its constructor or you might simply not care to access the object directly in your app.

[jonthom]

C++ has nothing to do with this. You don't need to assign the return value of new to be able to use the object. For instance the object might "install" itself on some other object in its constructor or you might simply not care to access the object directly in your app.

wysota is technically correct. However, both of these uses would generally be considered bad style and potentially dangerous. If you see a memory allocation like that, it is most likely a memory leak. Again, though, in this specific example, the ApplicationUI probably 'imprints' itself into the given Application object.