In article <[EMAIL PROTECTED]>, bruno at modulix <[EMAIL PROTECTED]> wrote:
>Lawrence D'Oliveiro wrote: >> In article <[EMAIL PROTECTED]>, >> "ToddLMorgan" <[EMAIL PROTECTED]> wrote: >> >>>I'm looking for the common types of mistakes that say a Java/C# or >>>even C++ developer may commonly make. >> >> Using subclassing when you don't have to. For instance, you might have a >> Java method which takes an argument of type java.io.OutputStream to >> which it writes. You might translate this to a Python method to which >> you are careful to only pass instances of subclasses of file objects. >> But in fact there is no necessity for this: you are free to pass any >> object which has appropriate members. >> >> I suppose this is an instance of the more general rule: "using OO when >> you don't have to". > >Lawrence, I'm afraid you're confusing OO with "statically-typed >class-based". FWIW, dynamic typing is part of OO since Smalltalk. I wasn't talking about dynamic typing, I was talking about subclassing, which is very much a part of OO. Unless you subscribe to the "OO is whatever looks like a good programming idea" definition <http://www.paulgraham.com/reesoo.html>. -- http://mail.python.org/mailman/listinfo/python-list
