Skip to main content

What happens if an error occurs in a constructor or destructor?

Constructors don't have a return type, so it's not possible to use error codes. The best way to
signal constructor failure is therefore to throw an exception. However, keep in mind that the
memory for the object itself is released, and the destructors for all sub-objects (i.e. members and
base classes) whose constructors have successfully run to completion will be called. The destructor
for the object being constructed will not be called.
For example (assume appropriate definitions):
class T
{
U u;
public:
T() { throw "Bye bye"; }
};
{
T * tptr=new T;
}
In this example, the memory allocated by operator new _will_ be released, and u's dtor will be
called.
class T2
{
U *uptr;
public:
T2() { uptr=new U; throw "Bye bye";}
~T2() { delete uptr; }
};
With this class, the memory occupied by T2 will be release, *BUT* T2's dtor will _not_ be
called, and the U object pointed to by uptr will be leaked.
Labels:

Comments

Post a Comment

https://gengwg.blogspot.com/

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checkin...
2 comments
Read more

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into ...
Post a Comment
Read more