Re: Static vs. Dynamic typing
From: Ilja Preuß (it_at_iljapreuss.de)
Date: 09/11/04
- Next message: Phlip: "Re: Questions of Designs"
- Previous message: Shashank: "Re: what's abstraction?"
- In reply to: Christopher Barber: "Re: Static vs. Dynamic typing"
- Next in thread: Isaac Gouy: "Re: Static vs. Dynamic typing"
- Reply: Isaac Gouy: "Re: Static vs. Dynamic typing"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 11 Sep 2004 09:00:44 +0200
Christopher Barber wrote:
> Without static checking this will only fail if the call is actually
> executed during testing. All it takes for the static check to fail
> is for the code to be compiled.
Correct.
> Without static checks it is more
> important that your tests cover every line of code and more
> thoroughly as well.
How much more important? How comfortable are you with the idea of a call
that's only checked by the compiler - without any check of the *semantics*
of the call?
> If you consider the static declarations
> themselves to be tests, then using them really shouldn't be any worse
> than writing tests.
If they wouldn't come with costs. But they do:
- they constrain the structure of the code,
- they increase compile time significantly, and thereby delay feedback from
the tests, and
- they tend to clutter the code with redundant information
These costs are significant in a mainstream language like Java.
Cheers, Ilja
- Next message: Phlip: "Re: Questions of Designs"
- Previous message: Shashank: "Re: what's abstraction?"
- In reply to: Christopher Barber: "Re: Static vs. Dynamic typing"
- Next in thread: Isaac Gouy: "Re: Static vs. Dynamic typing"
- Reply: Isaac Gouy: "Re: Static vs. Dynamic typing"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|