Re: [gobo-eiffel] Support for Xace in Gobo

On 3/12/2018 02:08, Berend de Boer wrote:
>>>>>> "Eric" =3D=3D Eric Bezault ericb@gobosoft com [gobo-eiffel] =

>>>>>> <[email protected]> writes:
> =

>  =A0=A0 Eric> So I'm wondering whether it is still worth supporting Xace
>  =A0=A0 Eric> in Gobo. I'm spending a lot of time trying to maintain Xace
>  =A0=A0 Eric> so that it can support new options introduced in ECF.=A0 Th=
is
>  =A0=A0 Eric> time could be better spent doing something else.=A0 So it
>  =A0=A0 Eric> might be time to stop supporting Xace and use ECF as primary
>  =A0=A0 Eric> Eiffel config file notation in Gobo.
> =

> I agree. As long as they are compatible...
> =

> But I'll switch to .ecf, and simply stick a notice in gexace that
> development has stopped, and new options will not be supported. That's
> good enough for me.

It's not a simple as that. I don't want to have to maintain to
set of files: .xace and .ecf for every library, every tool, every
example, every test. So the .xace files will soon become unusable
(if they reference a cluster that does not exist anymore, etc.).

So the tool gexace is one thing, but all the existing .xace files
in the Gobo package is also something to take into account.
And my gut feeling is that all .xace files out there processed
by gexace use in one way or another some .xace files from the
Gobo package. So keeping an unmaintained version of gexace
without maintaining the .xace files does not seem useful to me.

-- =

Eric Bezault
mailto:[email protected]
http://www.gobosoft.com

---------------------------------------------------------------------------=
---
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot