QSslEllipticCurve: don't call QSslSocketPrivate::ensureInitialized() in const functions

Rationale: the case of an invalid QSslEllipticCurve is already
dealt with before we'd call ensureInitialized(). But in order
to have a non-invalid QSslEllipticCurve, we must have called
one of the constructor functions first. There, we already call
ensureInitialized(), so we don't need to do it here again.

Change-Id: I96bdb5db63ec0165e6b8fac9469b5d81c6b2cdae
Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com>
bb10
Marc Mutz 2015-01-20 14:45:59 +01:00
parent 0c281bcc65
commit 95e9b93a77
1 changed files with 0 additions and 4 deletions

View File

@ -55,8 +55,6 @@ QString QSslEllipticCurve::shortName() const
if (id == 0)
return QString();
QSslSocketPrivate::ensureInitialized();
QString result;
#ifndef OPENSSL_NO_EC
result = QString::fromLatin1(q_OBJ_nid2sn(id));
@ -69,8 +67,6 @@ QString QSslEllipticCurve::longName() const
if (id == 0)
return QString();
QSslSocketPrivate::ensureInitialized();
QString result;
#ifndef OPENSSL_NO_EC
result = QString::fromLatin1(q_OBJ_nid2ln(id));