Anonymous committed bae1919

SF bug #1067018: Obsolete info in Tutorial 9.1

Removed a section that is out of date after type/class unification.
While there was still some validity, the paragraph offered more
confusion that insight.

  • Participants
  • Parent commits 9a1309a
  • Branches legacy-trunk

Comments (0)

Files changed (1)

 terms, since its object-oriented semantics are closer to those of
 Python than \Cpp, but I expect that few readers have heard of it.)
-I also have to warn you that there's a terminological pitfall for
-object-oriented readers: the word ``object'' in Python does not
-necessarily mean a class instance.  Like \Cpp{} and Modula-3, and
-unlike Smalltalk, not all types in Python are classes: the basic
-built-in types like integers and lists are not, and even somewhat more
-exotic types like files aren't.  However, \emph{all} Python types
-share a little bit of common semantics that is best described by using
-the word object.
 Objects have individuality, and multiple names (in multiple scopes)
 can be bound to the same object.  This is known as aliasing in other
 languages.  This is usually not appreciated on a first glance at