From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d89b08801f2aacae X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-30 14:41:22 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed1.cidera.com!Cidera!cyclone.socal.rr.com!cyclone3.kc.rr.com!news3.kc.rr.com!twister.socal.rr.com.POSTED!not-for-mail Message-ID: <3CCF0F92.FEB94EFC@san.rr.com> From: Darren New X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Is strong typing worth the cost? References: <4519e058.0204290722.2189008@posting.google.com> <3CCE8523.6F2E721C@earthlink.net> <3CCED46D.43145174@san.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 30 Apr 2002 21:40:13 GMT NNTP-Posting-Host: 66.75.151.160 X-Complaints-To: abuse@rr.com X-Trace: twister.socal.rr.com 1020202813 66.75.151.160 (Tue, 30 Apr 2002 14:40:13 PDT) NNTP-Posting-Date: Tue, 30 Apr 2002 14:40:13 PDT Organization: RoadRunner - West Xref: archiver1.google.com comp.lang.ada:23299 Date: 2002-04-30T21:40:13+00:00 List-Id: "Chad R. Meiners" wrote: > Changing requirements would require changing the auditing code which I would > gather is alot more costly than changing type information. Well, no, that's kind of the point. It's cheaper to change the auditing code than it is to change the type information, due to the way the whole process (including the language) is set up. > > You figure the cost of everything it takes to write the program that > > meets the requirements under realistic requirements. > > Invalid! (well mostly ;) How do we know the costs are related to strong or > weak typing? It could be that program A satisfies an unrequested > requirement that doubles the cost of development. "Doctor, Doctor! It hurts when I do this!" "Well, don't do that!" Of course you would have to know that your goal is to minimize the development effort, and therefore satisfying a number of unrequested requirements that take a great deal of work to satisfy is Bad. > I realize that your > realistic requirements MIGHT TRY to address this issue, but the better the > requirements the closer your programs get to being the same which is the > only way you can do a truly valid comparison. Well, I don't think it's reasonable to try to develop a program without strong typing in Ada. It just doesn't make sense, because Ada is strongly typed. You *can't* develop a weakly-typed program in Ada. So you would have to compare Ada against a weakly-typed language (or a dynamically-typed language) as a comparison, at which point your two programs won't be the same. Your requirements, of course, would have to deal with input and output, rather than program structure. And of course, the OP asked for some actual evidence, rather than lots of handwaving about why strong typing *should* be better. There's actually empirical evidence that dynamic typing is better in some situations, and one can point to many convincing theoretical reasons for strong typing being safer, and there are a number of axes to measure along, so I don't think there's any one answer. -- Darren New San Diego, CA, USA (PST). Cryptokeys on demand. The 90/10 rule of toothpaste: the last 10% of the tube lasts as long as the first 90%.