[EMAIL PROTECTED] wrote:

The strong vs. weak typing issue
is a different issue than compile vs runtime typing.

Agreed.

You actually have 4 combinations to choose from...

weak   typing + compile time typing ==> C
strong typing + compile time typing ==> Java
weak   typing + run     time typing ==> Perl

I might give you those.

strong typing + run     time typing ==> Python

Uh. No. Not even close. We're talking about the "Duck typing" language. As long as it has a "Quack" method, it's a duck. That doesn't count as strong typing.

strong typing + run time typing is something like Haskell.

Here's a real world example of something you can solve with it:
http://blog.moertel.com/articles/2006/10/18/a-type-based-solution-to-the-strings-problem

-a


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to