[Bf-python] Attribute casing

[Gilbert, Joseph]

Hmm.. well I'd personally prefer we stick with True and False but that
may screw with a lot of scripts.

-----Original Message-----
From: bf-python-bounces at projects.blender.org
[mailto:bf-python-bounces at projects.blender.org] On Behalf Of Ken Hughes
Sent: Friday, August 26, 2005 12:51 PM
To: Blender Foundation Python list
Subject: Re: [Bf-python] Attribute casing

Stephen Swaney wrote:
> On Fri, Aug 26, 2005 at 09:12:53AM -0400, Joseph Gilbert wrote:
> 
>>Yehoshua Sapir wrote:
>>
>>
>>>>Obj.attriubte = TRUE  (or)
>>>
>>>I'd like to note that Python already has a 'True' built-in.
>>>
>>>
>>
>>Hehe good point Yehoshua. It was just a way for testing and returning
1 
>>or 0 (which is what a lot of our functions were throwing and taking). 
>>It's probably better to be using 'True' and 'False' for booleans! :)
> 
> Actually, I believe it is more correct to say "Python *now* has a
> 'True' built-in".  And yeah, we should use it.

I was just thinking about while work on the tp_getset stuff.  For the 
attributes which and getStuff()/setStuff() methods which takes 1 or  0, 
should we also have them use booleans (setters would accept both bools 
and ints)?

Ken


_______________________________________________
Bf-python mailing list
Bf-python at projects.blender.org
http://projects.blender.org/mailman/listinfo/bf-python