2 ms·
> If you are testing such code you make sure to run it. Ahh, but that's not the problem. It's easy to test the code your changing, it's a much harder problem
by wvenable 17y ago
> If you are testing such code you make sure to run it.
Ahh, but that's not the problem. It's easy to test the code your changing, it's a much harder problem to find and test all the code that depends on that code. Having the compiler spit out every instance everywhere that you need to fix due to a new type-mismatch makes this significantly easier.
Some dynamic languages will happily convert values from one type to another even when that's not the desired result -- you might not get an error at all, just some bad data you might not find until much later.
- gte910h 17y ago>Some dynamic languages will happily convert values from one type to another even when that's not the desired result -- you might not get an error at all, just some bad data you might not find until much later. This happens with algol style static languages too (And is one of the reasons I find people arguing for Erlang instead of python more persuasive than those instead arguing C++ instead of ruby). You are confusing strong types with dynamic variables. Most of the algol languages have weak to medium type strength. For instance, python has much stronger types than C. However, it's variables are all dynamic references.