4 ms·
For a midsized to big project static typing is really nice. eg A few years ago I had a perl project that only let you know a function was missing at run time (
by ape4 13y ago
For a midsized to big project static typing is really nice. eg A few years ago I had a perl project that only let you know a function was missing at run time (ie when the user asked for that code).
- jfb 13y agoThat sounds ... less than great. I'm a fan of static typing, no question. I'm just not impressed with this article's handwaving.
- Mithaldu 13y agoThat's why you write a test suite and check that your test suite covers all code, using Devel::Cover.
- ape4 13y agoThanks I didn't know about that. Of course I used a test suite. But checking that all functions actually exist (in my case some had been renamed) is something you should not have to manually write.
- Mithaldu 13y agoWell, the idea is that your test suite should cover ALL code you have, so you don't have to check all your functions. Devel::Cover helps you by clearly marking code your tests don't run in red, so you know where you need to add tests and don't need to go through manually.