[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Looking for quote on static vs dynamic typing



> From: Michael Vanier [mailto:mvanier@cs.caltech.edu]
> Not me.  But it's interesting.  Usually the argument goes the 
> other way:
> 
>   Early on in a project, as code is rapidly evolving, you want dynamic
>   typing to keep as many design options open as possible. 
> When the code has
>   matured (it's well tested and not changing much), you want 
> more static
>   typing for efficiency and to help root out obscure bugs that may be
>   waiting to manifest themselves.
> 
> The Dylan language, for one, explicitly adopted the above philosophy.
> 
> Mike


Sorry (I wasn't as clear as I should've been).

I don't think someone on the list made the quote. I think that someone
posted (copied) the quote to the list, or a link to it.

Of course, it's possible that I came across it from some other source, and
I'm just hopelessly confused. OTOH, if there's a better group of people to
ask, I'd love to know...

I though the quote was interesting *because* it's the opposite of what you
think of as the usual argument.


*****************************************************************
The information in this email and in any attachments is 
confidential and intended solely for the attention and use 
of the named addressee(s). This information may be 
subject to legal professional or other privilege or may 
otherwise be protected by work product immunity or other 
legal rules.  It must not be disclosed to any person without 
our authority.

If you are not the intended recipient, or a person 
responsible for delivering it to the intended recipient, you 
are not authorised to and must not disclose, copy, 
distribute, or retain this message or any part of it.
*****************************************************************