🚀 go-pugleaf

Regarding tech note #164, I have two relavent stories:

1) When I moved to Ohio, a friend was showing me around.  Turning down a
certain street he said "now you'll see an example of mid-western road
repair."  Around the next bend was a sign saying "Dip in road."

2) When I discovered some problems in an IBM product once, I reported it and
received an interesting (and now, famous) reply: "Its not a bug, its a
feature!"

I'm not sure which story is more appropriate to this tech note, but I am sure
that I am very disappointed by the attitude this shows!

I don't care that the code will somehow work even if certain functions and
variables aren't declared explicitly.  Good software design dictates that
all objects be declared, especially in system software.  This is necessary
for portability (both imported software, and improved "macs of the future")
as well as debugging; Assuming something is an int because you can't find
a declaration is not the way I like to work!

A tech note that says "here's a bug we won't fix" (story #1), or that says
"its not a bug, its a feature" (story #2) is not particularly useful.
Obviously, people are complaining to you about this.  How 'bout a real
answer?

Wayne Pollock, The MAD Scientist
E-MAIL (Usenet):	...!{ihnp4, cbatt}!codas!usfvax2!pollock
	(GEnie):	W.POLLOCK