Hi, This is a mail for the purpose of formalizing a policy as it relates the the "stability" of relationships between classes in EFL. With EFL 1.23, Eolian is expected to become stable, which will mean that .eo files are effectively stable. There is not, however, a formal definition of what "stable" means in this context.
As an example, consider the following case where: * classes 'A', 'B', 'C' where 'C extends B' and 'B extends A' * 'B' implements method 'M' from 'A' Should having 'M' available to 'C' from its inheritance by 'B' be considered "stable" across releases, or can this be changed? Similarly, is this inheritance chain "stable", or can that be changed? This may seem like a clear-cut scenario to some, but it's important that a global policy is decided upon in advance of the release so that it can be documented and expectations can be set both for EFL itself as well as its users. I've created a tracking ticket (https://phab.enlightenment.org/T8209) where the policy decision will be recorded for historical purposes. Regards, Mike _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
