[Edu-sig] Design patterns

Arthur ajsiegel at optonline.net
Wed Aug 24 12:36:10 CEST 2005

> -----Original Message-----
> From: edu-sig-bounces at python.org [mailto:edu-sig-bounces at python.org] On
> Behalf Of Scott David Daniels

> Arthur wrote:
> > ... more to my point is the fact that I don't expect my programming
> language
> > to solve the problem of decoupling my API from my code. Because I don't
> > expect it to be a solvable problem.
> I don't know if I'm beating a dead horse, but I don't claim properties
> solves the problem of decoupling an API from its current implementation.
> I do claim it provides another tool to express a properly decoupled
> API.

Yup. You're beating a dead horse.

Everything I can find about properties in Java and C# relate it to
encapsulation and data hiding.

Everything I can find about Python relate that the language does not attempt
to support encapsulation and data hiding in the Java and C# sense.

I might be a dead horse who is dead wrong, but the issue about how
properties fit into Python is certainly not straightforward in the least,
and responding as if it were is grossly unfair - to the question raised.


More information about the Edu-sig mailing list