Dinamic vs Static: nessuna scusa.
Enri
L’esperto di Java per eccellenza (Bruce Eckel) scrive in un post non proprio recente (i grassetti sono miei):
In fact, what we need is
Strong testing, not strong typing.
So this, I assert, is an aspect of why Python works. C++ tests happen at compile time (with a few minor special cases). Some Java tests happen at compile time (syntax checking), and some happen at run time (array-bounds checking, for example). Most Python tests happen at runtime rather than at compile time, but they do happen, and that’s the important thing (not when). And because I can get a Python program up and running in far less time than it takes you to write the equivalent C++/Java/C# program, I can start running the real tests sooner: unit tests, tests of my hypothesis, tests of alternate approaches, etc. And if a Python program has adequate unit tests, it can be as robust as a C++, Java or C# program with adequate unit tests (although the tests in Python will be faster to write).
Quindi: attenzione a passare ai linguaggi dinamicamente tipati: non avrete nessuna scusa per non fare TDD!
Posted in Test Driven Development (TDD) |


March 2nd, 2010 at 3:00 pm
Îáùàÿ èíôîðìàöèÿ î Òóíèñå…
Äîñòîïðèìå÷àòåëüíîñòè Òóíèñà…