Re: Re: Oh my! Re: ECMA standard or forking the language?

[email protected]
Newsgroups gmane.comp.lang.eiffel.smalleiffel
Message-ID <OF434DE630.CA6A3165-ONC1256FF5.0023C2F0-C1256FF5.00249FC0@mpsa.com>
Hello,

> As Gobo works with SE 1.x, ISE 5.x, VE 4.x and VE 5.x, I think this is
> a very clear example who is forking and making incompatible changes to
> the Eiffel language.

Sure, but Gobo does not work (yet) with ECMA Eiffel, which is at least as 
far from any other Eiffel flavour than ours.

Certainly Gobo will evolve towards ECMA Eiffel since Eric belongs to the 
ECMA team, but I let him confirm (or refute) that.

> But I'm glad that we have a clear statement from the SE team now.

Please do remember that a fork has two branches. We fork from *ECMA* 
Eiffel. Or maybe ECMA Eiffel forks from Eiffel as we knew it till now. The 
point is not to know "who" forks. The point is that there *is* a fork. We 
used to have Eiffel, we now have ECMA Eiffel vs. SmartEiffel.

In other words: choose your side. SE or ECMA.

Best regards,
--
Cyril Adrian -- ALPLOG
@ PSA Peugeot Citroën, Sochaux, France
tél. +33 (0)3 81 33 48 76
fax +33 (0)3 81 33 16 06
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.