oship-dev team mailing list archive

["Sergio Miranda Freire" <sergio@xxxxxxxxxxxxxxx>]

Hi Eduardo,

 

Ever since Oship began, Tim has been complaining about this kind of problem.
In the first versions, he had arranged all classes in separated directories
and files, according to its package structure. Later for reasons that I
ignore he has moved to the current configuration. He had to change the
schema of some attributes in order to avoid the problem you have just
mentioned. In this case, parent in IEvent is defined as being an IObjectRef.
Possibly this may happen somewhere else. This was the solution Tim found. I
don´t know if there is an alternative. Maybe it is another case to go into
the implementation guide.

 

Cheers,

 

Sergio

 

De: oship-dev-bounces+sergio=lampada.uerj.br@xxxxxxxxxxxxxxxxxxx
[mailto:oship-dev-bounces+sergio=lampada.uerj.br@xxxxxxxxxxxxxxxxxxx] Em
nome de Eduardo César
Enviada em: sábado, 6 de março de 2010 01:44
Para: OSHIP-Dev
Assunto: [Oship-dev] Egg and chicken

 

Hi,

In datastructures.py, in the class IEvent, the attribute "parent" needs to
be defined as of type "IHistory".
But there is a catch because the class IHistory has some attributes that are
of type IEvent.

If I try to define "parent" with the correct type, the interpreter complains
that IHistory is not defined yet. If I exchange the order of the classes,
the interpreter complains that IEvent is not defined. Right now, "parent" is
defined of being of another type, for things to work.

I am wondering how I can solve this... someone has any hints?

Cheers
Eduardo