Spec clarification: can a signal and a method have the same name?

[Havoc Pennington]

Hi,

I think I'd classify this as "bad idea, if only because it's unclear to 
developers, but protocol does not check it so a binding could support it 
if it wanted to and in any case a binding should not blow up if it sees 
this"

Similarly, I think it's a good idea to avoid *common* keywords in 
*common* languages when naming stuff, and to avoid overloads. These 
things just cause pain. The protocol doesn't ban any of them though.

Havoc