Hans-Martin Mosner wrote:
> Alan Lovejoy wrote:
> > characters, but still not be ==.  And it works for message selectors, too!).


> I can imagine a couple of code readability problems when the message #foo, sent to
> an object of class Bar, means a totally different thing depending on the namespace
> in which the *sending* method was compiled.

Isn't the namespace concept meant do achieve this? At least if you allow
for parts of objects/classes (namely methods) to be in different
namespaces at the same time. So you could have several methods named
#foo in different namespaces with unique implementations in each one.
What you need to do though is to recompile (sending) messages when the
actual or imported namespace changes (or rather rebind the symbols).

Michael

-- 

 "To improve is to change, to be perfect is to change often." 
                                            Winston Churchill
+------------------------------------------------------------+
| Michael Rueger                                             |
| Phone: ++1 (818) 623 3283        Fax:   ++1 (818) 623 3559 |
+--------Michael.Rueger.-ND at online.disney.com----------------+