> Also, what's with the Magma requirement? just seeing maPrefixed
methods makes me feel uneasy, I don't know why... I think Magma broke
an image of mine when I first started using Squeak.


 Again, no Magma requirement.  Magma is nowhere in sight here.  "ma" does not mean Magma.
 
 The "ma" method prefixes are, quite simply, a namespace.  I was only trying to be polite by not hogging the namespace with my interpretation of general names like:
 
  Bag>>#maRemoveAll
     "Efficiently removes all elements in the receiver."
     ...
 
 instead of 
 
   Bag>>#removeAll
 
 So you can be assured that loading any of MY stuff should never stomp anything else you have loaded, whether it was "polite" with its own prefix or not.
 
 It's an ugly compromise to assure future interoperability with other code.  It was designed to make you feel MORE assured but it has apparently had the opposite effect; heh, probably because its "different" I presume..
 
 Regards,
   Chris