On 21 Apr 2008, at 09:17 , Christian Zagrodnick wrote:
> On 21.04.2008, at 08:58, Philipp von Weitershausen wrote:
>> On 21 Apr 2008, at 08:22 , Christian Zagrodnick wrote:
>>> The zope.i18nmessageid.Message class doesn't provide a specific
>>> interface.
>>>
>>> Is this intentional? I think it should provide an interface so we
>>> don't
>>> need to do isinstance(bla, Message) any more.
>>
>> In a way it's intentional: only the C implementation is immutable and
>> therefore secure against manipulation further down the line. That
>> said, we also have a Python implementation which takes over when
>> the C
>> implementation isn't available (which makes it really hard to test as
>> well...).
>
> Does C-Implementation mean we cannot declare an interface?
Sure we can: z.i.classImplements(Message, ISomeIface)
On 21 Apr 2008, at 09:17 , Christian Zagrodnick wrote: eid.Message class doesn't provide a specific
> On 21.04.2008, at 08:58, Philipp von Weitershausen wrote:
>> On 21 Apr 2008, at 08:22 , Christian Zagrodnick wrote:
>>> The zope.i18nmessag
>>> interface.
>>>
>>> Is this intentional? I think it should provide an interface so we
>>> don't
>>> need to do isinstance(bla, Message) any more.
>>
>> In a way it's intentional: only the C implementation is immutable and
>> therefore secure against manipulation further down the line. That
>> said, we also have a Python implementation which takes over when
>> the C
>> implementation isn't available (which makes it really hard to test as
>> well...).
>
> Does C-Implementation mean we cannot declare an interface?
Sure we can: z.i.classImplem ents(Message, ISomeIface)