First page Back Continue Last page Overview Graphics
This combination has a number of implications:
- Methods are not given privileged or implicit access to their first/"receiver" object. Really, all objects are the receivers, and they play different roles.
- Objects do not relate to methods in the same way that they do to their slots. Methods are cooperatively held between many objects, and each object must know what roles it can take in each method.
- self/super keywords are inappropriate conceptually; instead all arguments are referred to by names from the method signature, and changing the order of lookup is accomplished through messages to the context: resend, sendTo:, and sendTo:through:.