Difference between revisions of "Talk:Agent problems"
m |
|||
Line 12: | Line 12: | ||
I am aware that I am not the first one to be aware of this problem. But I am not sure whether this problem is revered to as a CAT call. When it is, and when the new CAT call solution will indeed be implemented, what are the consequences? You can only make agents to features with arguments of detachable type? | I am aware that I am not the first one to be aware of this problem. But I am not sure whether this problem is revered to as a CAT call. When it is, and when the new CAT call solution will indeed be implemented, what are the consequences? You can only make agents to features with arguments of detachable type? | ||
+ | |||
+ | --[[User:Ericb|Ericb]] 17:36, 11 April 2007 (CEST): I tried to compiled this code with Gobo's gec/gelint and I got this error: | ||
+ | |||
+ | [CATCALL] class FOO (10,14): type 'TUPLE' of actual argument #1 does not conform | ||
+ | to type 'TUPLE [B]' of formal argument in feature `item' in class 'FUNCTION [A, | ||
+ | TUPLE [B], C]' |
Revision as of 06:36, 11 April 2007
Is CAT Call
--Schoelle 09:26, 21 November 2006 (CET)
First comment: I assume you are missing a 'l_f := f'.
Second comment: this is a well known CAT call, caused by the (unsound) inheritance relation 'X[A] is subtype of X[B]' if 'A is subtype of B'.
--konradm
This article is in a very early state, so don't bother commenting to much on it. The intention is to list all the problems of the mechanism. Especially the fact that one has to type in a whole lot of type information for very little guarantees from the type system.
I am aware that I am not the first one to be aware of this problem. But I am not sure whether this problem is revered to as a CAT call. When it is, and when the new CAT call solution will indeed be implemented, what are the consequences? You can only make agents to features with arguments of detachable type?
--Ericb 17:36, 11 April 2007 (CEST): I tried to compiled this code with Gobo's gec/gelint and I got this error:
[CATCALL] class FOO (10,14): type 'TUPLE' of actual argument #1 does not conform to type 'TUPLE [B]' of formal argument in feature `item' in class 'FUNCTION [A, TUPLE [B], C]'