> Kirby Urner wrote:
> > Again, I think you're probably right, that this particular example is
> > perverse. Edu-sig is a scratch pad for bad ideas too. :-D
>
> Sorry, Kirby, I see we all seemed to jump on top of you here.
>
> --Scott David Daniels
> [EMAIL PROTECTED]
S'ok.
>From my point
> > So my general question is, as usual: wouldn't this be an interesting
> > and intelligent way to teach math?
<>
> I think it would be ... were it not for the following "facts":
>
> 1) subjects are taught in a compartimentalised way, leading to easy
> testing/grading ...
>
> you don't teach
I see your recipe made the Daily Python-URL today:
http://www.pythonware.com/daily/
I'm including your revisions in hypertoons24.py
http://www.4dsolutions.net/ocn/python/hypertoons/
Kirby
> Kirby Urner wrote:
> > Speaking of hypertoons, Scott sent me a cool refactoring of said module
> > us
Dethe Elza wrote:
On 27-Mar-05, at 2:04 PM, John Zelle wrote:
There is a good reason for these traditional guidelines, that is to
make the abstraction you are defining independent of its
implementation. Down the road, I might want to change the internal
representation of color, or remove or rena
On 31-Mar-05, at 3:53 PM, Beni Cherniavsky wrote:
There are still times when you don't want to expose attributes
directly, but getters and setters don't help you there either. For
example, if both myObj.x and myObj.y must be changed in synch to stay
valid, then they should be set via myObj.setX
