Dmitry Dorofeev wrote: > You still may use getter/setter style calls (with a price of performance) > by implementing doesNotUnderstand: aMessage Yea, but it's not pretty, and IMHO not something to be encouraged. I don't think the performance hit is as big a deal as the confusion it causes when debugging.