[Interface-dev] Re: another proposal

[Jim Fulton]

Steve Alexander wrote:
> 
>> First, because it looks ugly :). Somewhere deep down in the wiki we 
>> once agreed that classes are CamelCase, methods are camelCase and 
>> attributes are under_scored.
> 
> 
> No.  Glyph's proposal is correctly styled for Zope 3 code.
> 
> http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ClassesAttributesMethods 
> 
> 
> 
>> Second, I think interfaceName is yagni, interfaceObject is too long. 
>> If you really want the name, do method.interface.getName().
> 
> 
> Pragmatism 1, Demeter 0.
> 
> 
>> So, I'm for making Method.interface the interface object and nothing 
>> else. Provided that we're not really using it anywhere which I think 
>> is the case.
> 
> 
> I support this, as I have said in another email.

I was going to whine about the importance of backward compatability,
but the interface attribute is not documented in IMethod, so one
could argue that its private and subject to change. :)

So, I'm OK with this.  Whoever makes this change *should* update the interface.

When this is done, I'm happy to make a separate interface release
so that Twisted can use a released version of zope.interface. (Actually I'd
be even happier if someone else mase a release of zope.interface. :)

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org