|Subject:||Re: [certi-dev] Building CERTI on Ubuntu 15.10 (64bit)|
|Date:||Wed, 14 Oct 2015 14:04:01 +0200|
On 13/Oct - 18:36, Eric Noulard wrote:
> 2015-10-13 14:58 GMT+02:00 Åsmund Hjulstad <address@hidden>:
> > Hi,
> > $ gcc --version
> > gcc (Ubuntu 5.2.1-22ubuntu1) 5.2.1 20151010
> Strange enough on My Debian Strech 64 bits I have:
> $ gcc --version
> gcc (Debian 5.2.1-21) 5.2.1 20151003
> which compiles CERTI without trouble...
In any case, the warning is correct (and it would be very nice if gcc
decide to put it in this default set of warning).
In case of bad::alloc / bad::cast exception, the code will end with no
return value, so the caller will get an undefined return value. For
makeZero and decode method, a solution is to return nullptr, but for
rft, there is no good solution, but to really rethrow an exception.
Do you know why the exception throw is commented for this three methods
|[Prev in Thread]||Current Thread||[Next in Thread]|