lass::python::impl::PyShadowBaseWeak< CppBase > Struct Template Reference

a weak shadow class NEVER EVER owns the object, USE AT YOUR OWN RISK! Consult your local Lass::Python guru to gain insight when the use of this class is appropriate. More...

#include <pyshadow_object.h>

Public Types
typedef PyShadowBase< CppBase, true >	Type

---

Detailed Description

template<class CppBase>
struct lass::python::impl::PyShadowBaseWeak< CppBase >

a weak shadow class NEVER EVER owns the object, USE AT YOUR OWN RISK! Consult your local Lass::Python guru to gain insight when the use of this class is appropriate.

A rule of thumb is that any properly designed C++ interface should never be exposed using weak shadow objects. For your own safety, use weak shadow objects always in conjunction with the automatic object invalidator. This at least assures that when you access a weak shadow object from within Python that you don't get a dereference of a dangling pointer. You will notice that in Python a "C++ deleted" weak shadow object is transformed into None.

Definition at line 181 of file pyshadow_object.h.

---

Member Typedef Documentation

template<class CppBase >

typedef PyShadowBase<CppBase,true> lass::python::impl::PyShadowBaseWeak< CppBase >::Type

Definition at line 183 of file pyshadow_object.h.

---

The documentation for this struct was generated from the following file:

• pyshadow_object.h