Xref: utzoo comp.lang.c:26571 comp.software-eng:3060 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!cs.utexas.edu!uunet!mcsun!sunic!dkuug!iesd!iesd.auc.dk!fischer From: fischer@iesd.auc.dk (Lars P. Fischer) Newsgroups: comp.lang.c,comp.software-eng Subject: Re: Currency Quotes Message-ID: Date: 5 Mar 90 00:36:26 GMT References: <803@xyzzy.UUCP> <8229@hubcap.clemson.edu> Sender: news@iesd.auc.dk (UseNet News) Organization: Mathematics and Computer Science, University of Aalborg Lines: 20 In-reply-to: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu's message of 4 Mar 90 19:11:08 GMT In article <8229@hubcap.clemson.edu> billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu (William Thomas Wolfe, 2847 ) writes: > No, it was an example of the C community's cavalier attitude > toward software reliability. The comment "Don't base your > financial plans on the output", or words to that effect, were > a) inappropriate, since the static nature of the rates is part > of the specification and should not be listed in the defects > section, and b) irresponsible, since it indicates a flippant > approach to the reliability of the output. a) Yes, it's part of the specs, but it can't hurt to keep the user informed, can it? The user might not realize that using a static database has this effect. b) Nonsense. What would *you* have done? You might not like an occasional humorous remark, but calling it irresponsible is plain silly. /Lars -- Lars Fischer, fischer@iesd.auc.dk | Q: How does a project get to be one CS Dept., Univ. of Aalborg, DENMARK. | year late? A: One day at a time.