Re: [Liberty-eiffel] STRING not conforming to ANY

[Phil Malin]

Thanks Cyril.

That's actually a good read - thanks.  I guess I was thinking of exportability being tied to type-inheritance rather than inheritance in general - type and non-conforming.

Cheers,
Phil.

On 11/02/14 19:02, Cyril ADRIAN wrote:

Hi Phil,

2014-02-10 13:15 GMT+01:00 Phil Malin <address@hidden>:

Out of interest, how do you reconcile this with the export rule 'feature {ANY}' ?  Technically speaking, an object which inserts ANY instead of type-inheriting it shouldn't be able to view these features (perhaps the compiler doesn't let them - I haven't actually tried this).

Visibility is linked to inheritance, not conformance. See chapter 3.7 in http://wiki.liberty-eiffel.org/index.php/Papers#Non-Conforming_Inheritance:_the_SmartEiffel_Experiment_of_a_High-Level_Mechanism

 

I tried to find a better reference in the wiki but was not able to :-/

Cheers,

 

Cyril