Changes between Version 1 and Version 2 of Ticket #18
- Timestamp:
- 07/31/2008 10:06:58 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #18 – Description
v1 v2 1 At the moment, the RemoteInterface metaclass mechanism fully parses theRemoteInterface 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.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. 2 2 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 aRemoteInterface (to obtain a schema or enumerate the methods) should trigger the parsing.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.
