bugs

[Geoff Canyon]

On Apr 9, 2006, at 2:04 AM, David Vaughan wrote:

> As for my posts referring to your code, Geoff, I hoped I had made  
> it sufficiently clear already that I was using it as a jumping off  
> point to elaborate on the issues of what is a bug and differences  
> in user experiences, and nothing at all to do with your code which  
> I understood and accepted in the context in which you presented it.

Absolutely, no worries here.

This leads me to a question for those who agree with the following  
two statements:

  A. One line of code can be completely bug free -- regardless of  
whether or not my one line is in fact bug free ;-)
  B. It is (nearly) impossible to write large programs that are  
completely bug free.

The question is this: what do you think is the upper limit for  
_completely_ bug-free code?

Here is an example of something slightly larger than a single line  
(and actually useful) that I think is bug-free:

on stableSetSize pID,W,H
   -- sets the width and height of pID
   -- while keeping the topleft the same
   try
     put the rect of pID into tRect
   catch tSomeError
     exit stableSetSize
   end try
   if W is a number then put item 1 of tRect + W into item 3 of tRect
   if H is a number then put item 2 of tRect + H into item 4 of tRect
   set the rect of pID to tRect
end stableSetSize

Now someone point out to me that I've forgotten the built-in  
transcript property resizeFromTopLeft ;-)