[Bf-committers] Py/RNA API property class names.
ideasman42 at gmail.com
Tue Feb 15 13:09:33 CET 2011
understand that this may seem like dumbing things down but pointers
are so common in python and blender infact just about everything is a
pointer to allocated memory so its not a useful distinction.
x = (1, 2, 3) # eg is an a typle array of pointers to 3 PyObjects.
mesh = bpy.data.meshes # pointer to a mesh datablock
mesh["foo"] = "bar" # assignes a pointer to a char array.
Pointers are known to work as 'links' where both values point to the
same data, but with RNA defined properties not even this applies since
the values are local to each datablock and the data is never shared.
On Tue, Feb 15, 2011 at 11:30 AM, Doug Hammond
<doughammond at hamsterfight.co.uk> wrote:
> I would much prefer to keep the existing names than use the Custom*
> Whilst true that python doesn't normally deal with pointers as such, I still
> think that PointerProperty is a good name as it describes what the
> underlying C is doing. You shouldn't assume that python programmers don't
> know what a pointer is.
> IMO your proposed names are no clearer than the existing ones.
> On 15 Feb 2011 08:08, "Campbell Barton" <ideasman42 at gmail.com> wrote:
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers