[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-edu-sig
Subject:    [Edu-sig] Refocusing on Capabilities (was PySqueak)
From:       kirby.urner () gmail ! com (kirby urner)
Date:       2006-05-27 2:19:04
Message-ID: f604188c0605261919m26fe86d2l7e8a40df2f2f4fef () mail ! gmail ! com
[Download RAW message or body]

> As a language, no.  As a practice, *I* certainly would discourage it
> except when used internally as an implementation detail.

I agree that the DP (design pattern) generation is making better sense
around when to use and when not to use subclassing.  O'Reilly's 'Head
First Into Design Patterns' is a good example.  I plugged it in my
Saturday Academy class, along with TAOCP, NKS, and Zelle's Python
intro.

Here're some negative comments about this book that I liked, to help
us stay well rounded:
http://www.codinghorror.com/blog/archives/000380.html

Kirby

[prev in list] [next in list] [prev in thread] [next in thread]