Groklaw - Digging for Truth

	When you want to know more...

Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines

ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

You won't find me on Facebook

Donate

No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.

What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments

Sponsors

Hosting:

On servers donated to ibiblio by AMD.

Webmaster

Used to be standard operating procedure... | 91 comments | Create New Account

Comments belong to whoever posts them. Please notify us of inappropriate comments.

Used to be standard operating procedure...

Authored by: IANALitj on Monday, May 14 2012 @ 06:00 PM EDT

Good luck.

I was a consultant on a project, about thirty years ago. Another company's
consultants were also working for this client, and were working on software
separate from what I was working on.

When they got their code working, they removed the debugging statements.

Several months later, when I left the project, their "optimized" code
still wasn't working. I am not sure what their problem was, but obviously it
was subtle.

Such subtle bugs are common. (As just one example, it is easy for a typo to
cause data to be stored in the wrong place. Changing the length of one's code
could change the impact of such an error, to clobber a different place in
memory. If what is clobbered is an error message used only at system startup,
no harm is done. If what is clobbered is an instruction in a commonly used
subroutine, you are in trouble.)

[ Reply to This | Parent | # ]

Used to be standard operating procedure... - Authored by: eachus on Monday, May 14 2012 @ 10:39 PM EDT

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )