The Artima Developer Community
Sponsored Link

Design Forum
Dynamic versus Static Type Checking

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Dave Ford

Posts: 6
Nickname: dford
Registered: Jun, 2003

Dynamic versus Static Type Checking Posted: Jan 25, 2004 12:14 PM
Reply to this message Reply
Advertisement
In another thread, rubyfan made the following statement:

> In my experience programming in a dynamically-typed
> language makes it much easier to keep your architecture more
> flexible and amenable to a change in requirements



I like to think I'm open minded. But at the same time, I am skeptical of everything. On the surface, with my limited experience in dynamically-typed languages, I can guess the following:


1. If a change breaks something, the only way unit testing will find it is if you have 100% unit test coverage. Every method would need to be called with every possible param type, every field accessed, etc. This seems like more work than is necessary.


2. I can't see how refactoring IDEs could possibly be as intelligent as they are with , say IntelliJ, in a dynamically typed language.


So, I'm not debating his statement, because I don't have enough history yet with dynamically typed languages. But, could someone do me a favor and state why or how dynamically typed languages facilitate a more flexible and changeable architecture, in way that I can understand.


Dave Ford

Smart Soft - The Developer Training Company

http://www.smart-soft.com

Topic: Problem running Jini client!!!! Previous Topic   Next Topic Topic: J2EE Architecture Guidelines notes

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use