Article View: comp.lang.misc
Article #3288Re: Static typing: the OOP seatbelt
From: Jim Showalter
Date: Fri, 29 Mar 1991 22:09
Date: Fri, 29 Mar 1991 22:09
16 lines
1325 bytes
1325 bytes
>Any typing error that would be trapped in a staticly typed language
>can be captured in a dynamically typed languages using dataflow
>analysis.
But now you need an additional tool besides an editor, compiler, linker,
debugger. And what makes you think the programmer will always remember
to USE the dataflow analyzer? What if he/she is in a hurry? (Oh, right,
programmers NEVER cut corners to meet schedules...) The idea of the
"simple language aided and abetted with other tools" has been tried
with lint for C, with predictable results. You'll note that there is
no need for lint++ with C++, precisely because the C++ compiler does
the work instead. This is progress.
--
***** DISCLAIMER: The opinions expressed herein are my own, except in
the realm of software engineering, in which case I've borrowed
them from incredibly smart people.
Technical Details
Message-ID:
<jls.670284598@rutabaga>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!igor!rutabaga!jlsReferences:
<14160@life.ai.mit.edu> <1991Mar25.201620.5839@cua.cary.ibm.com> <27F11D7B.6309@tct.uucp> <49229@nigel.ee.udel.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!igor!rutabaga!jls From: jls@rutabaga.Rational.COM (Jim Showalter) Newsgroups: comp.lang.misc Subject: Re: Static typing: the OOP seatbelt Message-ID: <jls.670284598@rutabaga> Date: 29 Mar 91 22:09:58 GMT References: <14160@life.ai.mit.edu> <1991Mar25.201620.5839@cua.cary.ibm.com> <27F11D7B.6309@tct.uucp> <49229@nigel.ee.udel.edu> Sender: news@Rational.COM Lines: 16