Unexpected Behavior

Like any language, a Smalltalk programmer will encounter behavior that is completely unexpected, errors that send one running to the vendor (see also the wat talk).

Many of these events can be explained as a headspace error, a sanity check-list can help here:

• Was a method over-ridden that should have returned something, but did not?
• Are #hash and #= defined logically?
• Seaside
  • Is there something missing from the return value of #children - see this post
  • Registering a WAApplicaton too late
• Magritte
  • It may be obvious, however if a description does not have #beEditable then it will not show up
• Refactoring
  • Ensure that super initialize is sent from initialize when adding updating the parent of a class