Re: [Orbit-python-list] ORBit-Python 0.2.0 released

[Christian R. R. <ki...@as...>]

On 4 Apr 2001, Jason Tackaberry wrote:

> So I can see 3 different modes: strict, which forces you to comply with
> the mapping spec; extended, which implements stuff like transparent
> accessors, type coercion where it doesn't break the spec; and enhanced,
> which implements all the fancy features we want.  (These names are up
> for debate.)

The names and theory are okay with me. 

> I'm mostly thinking aloud here.  Please everyone chime in with comments.
> Once I organize my thoughts a bit better I'll consult the gurus on
> Python do-sig and gather their input.

So how did they react to the idea?

> object._set_value(object._get_value() + 2) is a little uglier but also a
> little more explicit.  In some ways, it's more readable.  So it's not as
> if the accessor methods are pointless in the face of the transparent
> ones.  But I think the choice should be there for ORBit-Python because
> nothing is sacrificed by providing it.

After 2000 lines of _get_value and _set_value the transparent accessors
look nice, you know? :-)

Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311