A belated postscript to this thread, because it's a more positive slant
that I didn't think of until revising some of the related documentation.
As remarked in my previous post, the automatic coerce methods that
caused Herve problems are generated from the assumption that contains=
in a class d
Hi John,
>
> John Chambers wrote:
>> Herve Pages wrote:
>>> Hi,
>>>
>>> It doesn't seem that the dispatching algo is finding my coerce
>>> method under
>>> some circumstances.
>>> Let's say I have 2 classes, A and AA and that AA is just a direct
>>> extension
>>> of A with no additional slots:
>>
Hi John,
John Chambers wrote:
> Herve Pages wrote:
>> Hi,
>>
>> It doesn't seem that the dispatching algo is finding my coerce method
>> under
>> some circumstances.
>> Let's say I have 2 classes, A and AA and that AA is just a direct
>> extension
>> of A with no additional slots:
>>
>>setCl
Herve Pages wrote:
> Hi,
>
> It doesn't seem that the dispatching algo is finding my coerce method under
> some circumstances.
> Let's say I have 2 classes, A and AA and that AA is just a direct extension
> of A with no additional slots:
>
>setClass("A", representation(ii="integer"))
>setCl
