[Bf-python] Blender.Group
Stephen Swaney
sswaney at centurytel.net
Fri Mar 17 02:11:18 CET 2006
On Thu, Mar 16, 2006 at 04:39:05PM -0800, Ken Hughes wrote:
> Martin Poirier wrote:
> >The only problem with using it is that the set
> >protocol is probably a python 2.4 feature of the
> >C/Python api, so people still on 2.3 will be majorly
> >pissed when they find out they can't even compile
> >anymore.
A valid point!
> But I thought what Cam was proposing here was
> to implement a custom BPy set class/object? In fact,
> why not implement this for Blender versions based on
> Python 2.3 and let versions based on 2.4 use the
> built-in set class?
I rather hate the idea of making a roll-your-own version
of something along with the "real" version. Duplicate code
that exists only to be thrown away and all that.
A couple thoughts:
1) #ifdefs in the code or switches in the build system that only
compile stuff for a particular version.
2) an addition Blender++ module with super-nify 2.4 features
that can be imported separately.
I *do* like the of doing the bitfields as a Set since that
fits the metaphor nicely.
--
Stephen Swaney
sswaney at centurytel.net
More information about the Bf-python
mailing list