home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!cam-eng!aci10
- From: aci10@eng.cam.ac.uk (A.C. Innes)
- Newsgroups: comp.os.os2.advocacy
- Subject: Re: Portable?
- Message-ID: <1992Jul27.200241.18211@eng.cam.ac.uk>
- Date: 27 Jul 92 20:02:41 GMT
- References: <1992Jul26.151507.14399@news.Hawaii.Edu>
- Sender: aci10@eng.cam.ac.uk (A.C. Innes)
- Organization: Cambridge University Engineering Department, England
- Lines: 27
- Nntp-Posting-Host: club.eng.cam.ac.uk
-
- In article <1992Jul26.151507.14399@news.Hawaii.Edu> tholen@galileo.ifa.hawaii.edu (Dave Tholen) writes:
- >Pete Skelly writes:
- [...]
- >> I suspect most other SE's will agree with the conclusion, that Bugs have a
- >> high probability of being introduced during translation.
- >
- >An increased probability, yes. How high it is depends on the talents of the
- >programmer.
-
- Could we please drop this thread? As Pete said, I think everyone will
- agree that rewriting tested code (whether translating assembler into
- C, or recoding to the specification from scratch) provides an
- *opportunity* to introduce errors (both new and "old" ones). Given
- this, I think everyone will also agree that it is *prudent* (ie. good
- software engineering practice) to *act as if* errors WILL be
- introduced -- in other words, to allow and budget time for finding and
- fixing errors, even though the original code had been thoroughly
- tested. How much time should be budgeted is a different question, and
- would likely depend on the individual programmer's skill, the
- company's programming practices, size and complexity (and
- critical-ness) of the code involved, etc.
-
- --
- Andrew Innes (aci10@eng.cam.ac.uk)
- Engineering Dept.
- Cambridge University
- Cambridge, England.
-