Changes between Version 1 and Version 2 of Ticket #18


Ignore:
Timestamp:
07/31/2008 10:06:58 AM (16 years ago)
Author:
Brian Warner
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18 – Description

    v1 v2  
    1 At the moment, the RemoteInterface metaclass mechanism fully parses the RemoteInterface specification before the class itself is defined. This makes it impossible to have methods which e.g. return instances of the same class (think graph-traversal interfaces: A.get_children() returns more instances of A). Likewise, it is impossible to have two classes mutually reference each other.
     1At the moment, the !RemoteInterface metaclass mechanism fully parses the !RemoteInterface specification before the class itself is defined. This makes it impossible to have methods which e.g. return instances of the same class (think graph-traversal interfaces: A.get_children() returns more instances of A). Likewise, it is impossible to have two classes mutually reference each other.
    22
    3 To fix this, the parsing of the methods inside the RemoteInterface should be put off as long as possible. The first time that someone uses a RemoteInterface (to obtain a schema or enumerate the methods) should trigger the parsing.
     3To fix this, the parsing of the methods inside the !RemoteInterface should be put off as long as possible. The first time that someone uses a !RemoteInterface (to obtain a schema or enumerate the methods) should trigger the parsing.