OO in Python? ^^

Torsten Bronger bronger at physik.rwth-aachen.de
Sun Dec 11 04:26:29 EST 2005


Hallöchen!

Matthias Kaeppler <void at void.com> writes:

> [...]
>
> Another thing which is really bugging me about this whole
> dynamically typing thing is that it seems very error prone to me:
>
> foo = "some string!"
>
> # ...
>
> if (something_fubar):
>    fo = "another string"
>
> Oops, the last 'o' slipped, now we have a different object and the
> interpreter will happily continue executing the flawed program.
>
> I really see issues with this, can anyone comment on this who has
> been working with Python more than just a day (like me)?

There are even a couple of further checks which don't happen
(explicitly) in a dynamic language like Python, and which do happen
in most statically typed languages like C++.  And yes, they are a
source of programming mistakes.

However, in everyday programming you don't feel this.  I don't make
more difficult-to-find mistakes in Python than I used to make in my
C++ code.  But what you do feel is the additional freedom that the
dynamic approach gives to you.

Basically it's a matter of taste and purpose whether you want to be
controlled heavily or not.  Python is particularly liberal, which I
appreciate very much.

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus            ICQ 264-296-646



More information about the Python-list mailing list