Handling of WPF interfaces subtleties
Objects created for the .NET environment must usually expose feature Equals, an implementation of the interface specified in .NET documentation as follow (warning, C# syntax incoming):
public virtual bool Equals( Object obj )
EiffelStudio provides a default implementation if the source code of a .NET Eiffel project doesn't.
For most projects this is fine, however it becomes a problem for classes that inherit from the WPF graphic classes, because those have a different definition of Equals, that must not be redefined. Yet, if the source code doesn't redefine Equals, then the compiler will do it by default.
This support is located in lines 1537 to 1544 of cil_code_generator.e in the compiler source code.
I'm requesting that the Eiffel compiler for .NET analyze whether it must provide a default implementation of Equals (and possibly other features) depending on parent assemblies, instead of always doing it like today.
Benefits: with this change, applications taking advantage of the WPF user interface become, if not practical, at least possible.