🚀 go-pugleaf

"Tristan Reeves" <moonshine@apex.net.au> wrote in message
news:1024306483.86878@web.apex.net.au...
>
>
> Of course it is an ugly problem in the language, even if not a
show-stopper.
>
> Just because you haven't encountered one doesn't mean there will never be
a
> name clash. It doesn't matter how carefully you choose your method names;
> different domains use the same word for different concepts, besides which
it
> is ridiculous to have to tweak method names like "Open" or "Draw" - which
> are perfectly fine - just because someone else *might* be using them.
Trying
> to puzzle out whether or not a given word is in use in some unknown
> interface somewhere else on this planet is fruitless. At best you can
hope.
>
> Even if name-clashes are rare, it seems to me that there is just no good
> reason why a name resolution technique could not have been implemented in
> the language.
>
>

I agree with Laurence that this is only a minor problem (and in practice a
very rare one at that). This is partly because a clash only occurs if the
method name AND signature match. So in the rare cases that a clash does
occur we have to use delegation. I think this is quite a small price to pay
for avoiding the extra complication of name resolution. With a reasonable
JIT the run time cost of delegation is negligible.

Mark Thornton