Re: [gobo-eiffel-develop] gobo ecf

[Martin S. <se...@et...>]

Dear Eric,

I just want to express that I feel very unhappy about how you acted in the ECF discussion over the past year.

I personaly hated Ace since I had to deal with it in my first year at ETH.
I _like_ ECF. I do not force you to like it... I respect your opinion.
But you do not respect mine.

I want ECF. I want ECF support in _all_ gobo tools.

This is the need of your users. And I think it is time for pragmatism.

Not having support for it caused me and others already enough pain.
And now you tell me that actually code exists but you don't release it?
This is a punch in the face of your users...

You are the BDFL (http://en.wikipedia.org/wiki/Benevolent_Dictator_for_Life) and abuse your position
by refusing to incorporate patches by others into the repository which were a first step
into the direction to support ECF in gobo.
You act very much against the way open source projects work.
I simply feel that gobo is _not_ open enough.
There was more than one attempt of people to add this support to gobo, but you blocked it.
And now you did it again.

How do others think about it? I think it is definitly time to make progress.

regards,

  Martin


On Sat, 14 Jul 2007 18:02:10 +0200
Eric Bezault <er...@go...> wrote:

> 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
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop

-- 
/*
 * martin seiler
 * se...@et...
 */
-- 
/*
 * martin seiler
 * se...@et...
 */