Put one of the pointers in KNS::Engine in the d-pointer and normally store the
d-pointer as a class member, instead of doing it statically.
Details
Details
- Reviewers
leinir mwolff - Group Reviewers
Frameworks - Commits
- R304:d659619e0c96: Remove KNS::Engine d-pointer hack
Tests still pass, discover still runs
Diff Detail
Diff Detail
- Repository
- R304 KNewStuff
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
Hmmmm... this is tricky, but... yes, it seems reasonable to me that replacing one pointer with another would cause no BIC issues... and i certainly am happy to get rid of the d-pointer hack, so... if we're absolutely super-sure that this is BC, i'm all for it... would kind of like someone with better linker-fu to give word on this, but in principle, i like :)