trapper1 Loc: Southside Virginia

I made the statement in an earlier post about the "unwritten" prohibition of using all-caps. I see I have been corrected and for that I am appreciative. I did not even know that whole gamut of instructions from admin existed but have now read the protocols and better understand what is expected and required. Changing the course and getting back to the OP's point that programs should be bug free when first issued and the resulting replies pointing out the difficulty of achieving such a task reminded me of the WW 2 incident when the Navy was procuring a new dive bomber to replace the SBD. The leading contender was Curtis Aircraft whose entry was known as the SB2C (Scout Bomber 2 Curtis) Helldiver, a name which was immediately converted by the always irreverent Navy personnel to Son Of A Bitch Second Class. When Curtis submitted the SB2C to the Navy for acceptance, the Navy rejected it because they uncovered, are you ready, 800 defects in the aircraft. The aircraft survived this rejection and went on to become a very serviceable unit for the Navy. The point is that no matter how much testing is done, the more complex the subject the more flaws that can be expected to emerge when the item is released for acceptance and no person or company can possibly anticipate any or all problems that might arise when the item hits the streets.

lukevaliant Loc: gloucester city,n. j.