> >> I tried a = BN_dup(b);
> >>
> >> if b is NULL, it causes error. Is this normal or should it just
> >> duplicate NULL over to a?
> > It's at times like this that I wish they hadn't made && boolean.
> > Wouldn't it be cool to write:
> >
> > a=b && BN_dup(b);
> >
> > ? (Works in Perl, BTW).
> The equivalent in C is only slightly more verbose:
>
> a = b ? BN_dup(b) : NULL;
I think
(a=b) && (a=BN_dup(b));
is something Ben will be more happy about ;-)
But back to the original question. I think it's really
Bug and should be handled by BN_dup() internally.
--
Holger Reif Tel.: +49 361 74707-0
SmartRing GmbH Fax.: +49 361 7470720
Europaplatz 5 [EMAIL PROTECTED]
D-99091 Erfurt WWW.SmartRing.de
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
