-
Committer:
Manuel Moos
-
Date:
2019-07-26 21:20:02 UTC
-
Revision ID:
z-man@users.sf.net-20190726212002-m6jtxppq1uoo2cq0
Better: use nObserverPtr to check for deletion of no
This avoids the trouble the previous commit would have caused
if no gets destroyed, but an entirely new object gets created in its
place.
I'd use nObserverPtr for the current object no itself, but
nObserverPtr only is for const pointers.