Operands and operators should be pythonic

Registered by Gustavo Narea on 2009-06-23

Operations should expose a more pythonic API, to make things more pleasant when handling the operands directly. To build an equality operation, for example, one must do `Equal(operand1, operand2)` -- `operand1 == operand2` doesn't work. As a consequence, Booleano operands must implement the so-called "rich comparison methods" so these expressions can be used (e.g., `operand1 == operand2` will be transformed under-the-hood into `Equal(operand1, operand2)`). All the operators must be implemented, unless there's no Python equivalent.

Blueprint information

Status:
Complete
Approver:
Gustavo Narea
Priority:
Not
Drafter:
Gustavo Narea
Direction:
Approved
Assignee:
Gustavo Narea
Definition:
Obsolete
Series goal:
Accepted for trunk
Implementation:
Blocked
Milestone target:
milestone icon 1.0a2
Started by
Gustavo Narea on 2010-04-01
Completed by
Gustavo Narea on 2010-04-01

Related branches

Sprints

Whiteboard

This no longer sounds like a good idea. It'd just contribute to confuse people about Booleano datatypes vs Python datatypes.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.