<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Implement digital signature support (qt frontends)" href="https://bugs.freedesktop.org/show_bug.cgi?id=94378#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Implement digital signature support (qt frontends)" href="https://bugs.freedesktop.org/show_bug.cgi?id=94378">bug 94378</a> from <a class="email" href="mailto:aacid@kde.org" title="Albert Astals Cid <aacid@kde.org>"> Albert Astals Cid</a> <pre>(In reply to Hanno Meyer-Thurow from <a href="show_bug.cgi?id=94378#c11">comment #11</a>) > (In reply to Albert Astals Cid from <a href="show_bug.cgi?id=94378#c10">comment #10</a>) > > + private: > > + SignatureStatus signature_status; > > + CertificateStatus certificate_status; > > + > > + QString signer_name; > > + time_t signing_time; > > > > This is still bad, you need to have just a d-pointer as private member in > > there and then that pointer containing the rest of members. > > Whatever a d-pointer is. google for it, it's a quite common name/construct, that's why i asked if you knew what it was a few comments ago. > To simplify, SignatureValidationInfo class may just > receive the pointer to core SignatureInfo instance. Query and return the > info from core SignatureInfo. > > Would that be okay? You can store the SignatureInfo in the d-pointer if you want, we still want a d-pointer to make it easier to maintain binary compatibility.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>