It's perfectly safe to delete NULL pointers, so simplify things by removing these checks.tags/v1.11.90
CSecurityStack::~CSecurityStack() | CSecurityStack::~CSecurityStack() | ||||
{ | { | ||||
if (state0) | |||||
delete state0; | |||||
if (state1) | |||||
delete state1; | |||||
delete state0; | |||||
delete state1; | |||||
} | } | ||||
bool CSecurityStack::processMsg() | bool CSecurityStack::processMsg() |
CSecurityVeNCrypt::~CSecurityVeNCrypt() | CSecurityVeNCrypt::~CSecurityVeNCrypt() | ||||
{ | { | ||||
if (availableTypes) | |||||
delete[] availableTypes; | |||||
delete[] availableTypes; | |||||
} | } | ||||
bool CSecurityVeNCrypt::processMsg() | bool CSecurityVeNCrypt::processMsg() |
SSecurityStack::~SSecurityStack() | SSecurityStack::~SSecurityStack() | ||||
{ | { | ||||
if (state0) | |||||
delete state0; | |||||
if (state1) | |||||
delete state1; | |||||
delete state0; | |||||
delete state1; | |||||
} | } | ||||
bool SSecurityStack::processMsg() | bool SSecurityStack::processMsg() |
SSecurityVeNCrypt::~SSecurityVeNCrypt() | SSecurityVeNCrypt::~SSecurityVeNCrypt() | ||||
{ | { | ||||
delete ssecurity; | delete ssecurity; | ||||
if (subTypes) { | |||||
delete [] subTypes; | |||||
subTypes = NULL; | |||||
} | |||||
delete [] subTypes; | |||||
} | } | ||||
bool SSecurityVeNCrypt::processMsg() | bool SSecurityVeNCrypt::processMsg() |