In a message of Fri, 26 Aug 2005 18:24:33 EDT, Arthur writes:
And am hoping he is quite wrong in the assessment that information hiding
is a base requirement for information science. ;)
He is quite correct, but 'hiddenness' is not an infinite human good,
such as health. It is quite possible to
-Original Message-
From: Laura Creighton [mailto:[EMAIL PROTECTED]
One nice thing about overwriting __getattr__ and __setattr__ is
that when you are done you have something that fairly shrieks
'black magic here'. Properties look innocuous. Some people go quite
nuts with them,
-Original Message-
From: Laura Creighton [mailto:[EMAIL PROTECTED]
My guess is that you think that properties violate 'Explicit is better
than implicit.'
Not exactly.
More like I think that it encourages theory, and I appreciate Python as
a-a-theoretical.
The counter argument is
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin
Costabel
Sent: Saturday, August 27, 2005 9:49 AM
To: Visualpython-users
Subject: [Visualpython-users] Visualpython 3.2.1 for Mac OSX 10.4 now in
Fink
There is now a Fink package for vpython version
Separating these matters in an educational setting is more than
problematic.
Art
In an educational setting, I use analogies.
Think of interacting with a waiter in a restaurant. Your expectation is you
name the foods and drinks you want, and after a period of time, those items
arrive at
-Original Message-
From: Kirby Urner [mailto:[EMAIL PROTECTED]
Information hiding means sparing me the details. In an open source
world,
I might be able to see those details if I really cared about them. In the
case of a private bank, fat chance.
Yes, we are at the core of
In my MVC example, the Viewer expected a 'shape' object to support a
specific API: verts and edges needed to be available as attributes.
Let me try to practice better what I think I am preaching and follow your
lead in making the discussion more concrete and less theoretical.
I have a line
Arthur wrote:
I have a line segment - defined as the segment connecting 2 points. The
interface allows the points to be picked and moved.
The line segment has a length. I choose line.getLength() as my API
Am I - in fact - violating the Uniform Access Principal.
If I am, am I
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Scott David Daniels
My strongest reaction has
to do with your wish to deny me the ability to make another choice
If that is a reference to my opinion about the visibility of the built-in
property
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Scott David Daniels
If I am not violating the Uniform Access Principal how do we express on
what
basis I am not?
This to me has to do with the set of calls in your API.
Yes but according to
10 matches
Mail list logo
