Re: Code/test ratio wrt static vs dynamic typing [was: Re: Python Success stories]

2008-05-20 Thread greg
Someone wrote: I'm just curious whether this argument against dynamic typing - that you end up doing the job of a static compiler in test code - holds in practice. I suspect that, although some of the things caught by the tests would be caught by static typing, the very *same* tests are also

Re: Code/test ratio wrt static vs dynamic typing [was: Re: Python Success stories]

2008-04-30 Thread cokofreedom
A rather off-topic and perhaps naive question, but isn't a 1:4 production/test ratio a bit too much ? Is there a guesstimate of what percentage of this test code tests for things that you would get for free in a statically typed language ? I'm just curious whether this argument against

Re: Code/test ratio wrt static vs dynamic typing [was: Re: Python Success stories]

2008-04-30 Thread MRAB
On Apr 30, 10:47 am, [EMAIL PROTECTED] wrote: A rather off-topic and perhaps naive question, but isn't a 1:4 production/test ratio a bit too much ? Is there a guesstimate of what percentage of this test code tests for things that you would get for free in a statically typed language ? I'm

Code/test ratio wrt static vs dynamic typing [was: Re: Python Success stories]

2008-04-29 Thread George Sakkis
On Apr 29, 2:25 pm, Fuzzyman [EMAIL PROTECTED] wrote: There are around 30 000 lines of Python in the production code and about 120 000 lines of Python code in the test framework. A rather off-topic and perhaps naive question, but isn't a 1:4 production/test ratio a bit too much ? Is there a