Re: [gobo-eiffel-develop] gobo ecf

[Eric B. <er...@go...>]

Hi Thomas,

Thomas Delaet wrote:
> I'm interested in completing ECF support in Gobo. The main reason is 
> that it would be nice to have for my phd project which uses erl-g (which 
> in turn relies on gobo for parsing system control files).
> 
> Based on the code, I understand that the only thing left for ECF support 
> is implementing a parser that populates the ET_ECF_UNIVERSE class. Is 
> this correct? Do you have any hints on this process? I looked at the 
> framework/configuration/parser directory in estudio svn and I guess I 
> could reuse most of it. That leaves only the process of converting the 
> created data-structures in ET_* datastructures ...

If you followed the discussions on the gobo-eiffel-develop mailing
list during the past year or so, you would know that I was very much
against the introduction of ECF as a replacement of Ace. Therefore
I'm not ready to let people waste their time trying to make Gobo
support ECF. I don't say that Gobo will never support ECF, just that
I'm not ready for the idea yet. The only reason why there are ECF
skeleton classes in Gobo is because my employer paid me to do so.
I know how to plug ISE's ECF parser to populate ET_ECF_UNIVERSE.
I was paid to do so. But I'm very sorry, I'm not ready to show people
how to do it, neither to integrate that code into Gobo.

Also note that having full support for ECF in Gobo is not just
about using an ECF parser to populate ET_ECF_UNIVERSE. There are
functionalities which have changed between Ace and ECF. For example
the introduction of libraries and the way class name clashes are
handled (or ignored).

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com