resource-cleanup | 易学教程

Should objects delete themselves in C++?

阅读更多关于 Should objects delete themselves in C++?

I've spent the last 4 years in C# so I'm interested in current best practices and common design patterns in C++. Consider the following partial example: class World { public: void Add(Object *object); void Remove(Object *object); void Update(); } class Fire : Object { public: virtual void Update() { if(age > burnTime) { world.Remove(this); delete this; } } } Here we have a world responsible for managing a set of objects and updating them regularly. Fire is an an object that might be added to the world under many different circumstances but typically by another object already in the world. Fire

How can I get around the lack of a finally block in PHP?

阅读更多关于 How can I get around the lack of a finally block in PHP?

问题 PHP prior to version 5.5 has no finally block - i.e., whereas in most sensible languages, you can do: try { //do something } catch(Exception ex) { //handle an error } finally { //clean up after yourself } PHP has no notion of a finally block. Anyone have experience of solutions to this rather irritating hole in the language? 回答1: Solution, no. Irritating cumbersome workaround, yes: $stored_exc = null; try { // Do stuff } catch (Exception $exc) { $stored_exc = $exc; // Handle an error } //

Should objects delete themselves in C++?

阅读更多关于 Should objects delete themselves in C++?

问题 I've spent the last 4 years in C# so I'm interested in current best practices and common design patterns in C++. Consider the following partial example: class World { public: void Add(Object *object); void Remove(Object *object); void Update(); } class Fire : Object { public: virtual void Update() { if(age > burnTime) { world.Remove(this); delete this; } } } Here we have a world responsible for managing a set of objects and updating them regularly. Fire is an an object that might be added to