Static Typing #
From Matz blog ( 2005-01-04, 2005-01-07, 2005-01-20 ).
Matz introduced and commented on Guido’s blog articles about Optional Static Typing on Python ( 1, 2, 3, 4 ) in these days. He talked up the early idea than latest one.
On Ruby, he made up his mind NOT to add Static Typing. Because he thinks the “optional” one is down by half and the “full” one lead to losing Ruby’s identity by dynamic language, even if it’s friendly for dynamic language. Besides, He concerned about its complexity, implements and performance as against its effect.
But he is ready to add Type Checking System if there is a good idea. He thinks that it’ll be the one like current C Extention’s type checking. He has an interest in friendly Duck-Typing, Object Adaptation, Design by Contract.
Joao Pedrosa
It’s great to get to know what Matz thinks about this issue. I agree with him, we shouldn’t hurry and lose what we have conquered.
babie
Oops, I missed. Please sub(/identity by dynamic language/, “identity as dynamic language”)
gab
did I already said how long I’ve been dreaming of someone reporting from matz blog? thanks a lot for this :)
Comments are closed for this entry.