Re: CML2 1.4.0, aka "brutality and heuristics"

2001-05-06 Thread Matthias Andree

On Fri, 04 May 2001, Eric S. Raymond wrote:

> Sigh...now, I hope, we can get back to solving problems that I don't
> expect to be so rare they're lost in the statistical noise.  It's not
> good to get so obsessed about finding clever solutions to corner cases
> that one loses sight of the larger issues.

The problem about rare cases is that they don't get proper testing, so
bugs may slip through and go unnoticed for an extended amount of time
without even being documented.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: CML2 1.4.0, aka brutality and heuristics

2001-05-06 Thread Matthias Andree

On Fri, 04 May 2001, Eric S. Raymond wrote:

 Sigh...now, I hope, we can get back to solving problems that I don't
 expect to be so rare they're lost in the statistical noise.  It's not
 good to get so obsessed about finding clever solutions to corner cases
 that one loses sight of the larger issues.

The problem about rare cases is that they don't get proper testing, so
bugs may slip through and go unnoticed for an extended amount of time
without even being documented.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



CML2 1.4.0, aka "brutality and heuristics"

2001-05-04 Thread Eric S. Raymond

The latest version is always available at http://www.tuxedo.org/~esr/cml2/

Release 1.4.0: Fri May  4 18:18:15 EDT 2001
* Ugly hack for recovery from inconsistent configurations.

We've spent a lot of time and effort recently arguing about elaborate
recovery algorithms for the extremely unusual case that the CML2
configurator loads a configuration that has become invalid because of
a constraint added to the rulebase since the configuration was
written.  (Mere addition of new symbols doesn't trigger this.)

The general problem is theoretically hard and for practical purposes
insoluble, so I've have implemented a suggestion by Dave Wagner and
John Stoffel.  CML2 will now try to recover fom a load-time
inconsistency by smashing all the non-frozen symbols in the violated
constraint to the value N (and notifying the user that it's doing so).
This is ugly, but will handle most cases.  In the few it doesn't
handle, the bindings loaded from the file will be backed out as a
unit.  In any case the user will be left in a running configurator.

Sigh...now, I hope, we can get back to solving problems that I don't
expect to be so rare they're lost in the statistical noise.  It's not
good to get so obsessed about finding clever solutions to corner cases
that one loses sight of the larger issues.
-- 
http://www.tuxedo.org/~esr/;>Eric S. Raymond

The prestige of government has undoubtedly been lowered considerably
by the Prohibition law. For nothing is more destructive of respect for
the government and the law of the land than passing laws which cannot
be enforced. It is an open secret that the dangerous increase of crime
in this country is closely connected with this.
-- Albert Einstein, "My First Impression of the U.S.A.", 1921
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



CML2 1.4.0, aka brutality and heuristics

2001-05-04 Thread Eric S. Raymond

The latest version is always available at http://www.tuxedo.org/~esr/cml2/

Release 1.4.0: Fri May  4 18:18:15 EDT 2001
* Ugly hack for recovery from inconsistent configurations.

We've spent a lot of time and effort recently arguing about elaborate
recovery algorithms for the extremely unusual case that the CML2
configurator loads a configuration that has become invalid because of
a constraint added to the rulebase since the configuration was
written.  (Mere addition of new symbols doesn't trigger this.)

The general problem is theoretically hard and for practical purposes
insoluble, so I've have implemented a suggestion by Dave Wagner and
John Stoffel.  CML2 will now try to recover fom a load-time
inconsistency by smashing all the non-frozen symbols in the violated
constraint to the value N (and notifying the user that it's doing so).
This is ugly, but will handle most cases.  In the few it doesn't
handle, the bindings loaded from the file will be backed out as a
unit.  In any case the user will be left in a running configurator.

Sigh...now, I hope, we can get back to solving problems that I don't
expect to be so rare they're lost in the statistical noise.  It's not
good to get so obsessed about finding clever solutions to corner cases
that one loses sight of the larger issues.
-- 
a href=http://www.tuxedo.org/~esr/;Eric S. Raymond/a

The prestige of government has undoubtedly been lowered considerably
by the Prohibition law. For nothing is more destructive of respect for
the government and the law of the land than passing laws which cannot
be enforced. It is an open secret that the dangerous increase of crime
in this country is closely connected with this.
-- Albert Einstein, My First Impression of the U.S.A., 1921
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/