[MPlayer-cvslog] CVS: main configure,1.1197,1.1198

[Ivan Kalvachev]

2006/5/13, Diego Biurrun <diego at biurrun.de>:
> On Sat, May 13, 2006 at 06:53:16PM +0300, Ivan Kalvachev wrote:
> > 2006/5/13, Diego Biurrun <diego at biurrun.de>:
> > >On Sat, May 13, 2006 at 06:31:11PM +0300, Ivan Kalvachev wrote:
> > >> 2006/5/13, Diego Biurrun <diego at biurrun.de>:
> > >> >
> > >> >There are about 150 --enable parameters.  You want to change the
> > >> >semantics of one of them.  If this is not a hack, then we will have to
> > >> >find another word for it.  Whatever you wish to call it, it is not
> > >> >acceptable.
> > >>
> > >> I still don't understand why it is not acceptable. Because it doesn't
> > >> "look" like the others?
> > >
> > >No, because the semantics are different.  150 --enable parameters work
> > >one way, 1 works different from the others.
> >
> > I don't get this thing with the semantics. What is the semantics? And
> > why is it so important? So important that you have to break code and
> > then hack code around to preserve it.
>
> http://en.wikipedia.org/wiki/Semantics
>
> In short, semantics is the meaning of something.  The --enable
> parameters set a variable to yes and thus force the feature on, skipping
> autodetection.  Forcing autodetection instead is an entirely different
> meaning.

I didn't ask what semantics mean, I asked what is the semantics of configure.
You doesn't seem to know.

> This discussion ends here for me.  We have already wasted far too much
> valuable time over nothing.  My decision is final, I will not accept one
> parameter behaving different from the others.

It does NOT.

What I am trying to explain to you, is that the current semantics is:
 If option is autodetected then --enable will force it.
 If option is disabled then  --enable will autodetect it.

That's why all options that have check (they are few indeed) do
perform check on "yes" and there is no way to force them (e.g. gui).

Semantics can be changed, can you change your altitude?