Status updates for feature freeze

[Kevin E Martin]

On Fri, Aug 06, 2004 at 02:08:34PM -0400, Kevin E Martin wrote:
> On Fri, Aug 06, 2004 at 10:04:08AM -0700, Keith Packard wrote:
> > 
> > Around 12 o'clock on Aug 6, Michel =?ISO-8859-1?Q?D=E4nzer?= wrote:
> > 
> > > >    Each Option line lists one extension and a value (either "enable" or
> > > >    "disable").  The value is not case sensitive, but the name of the
> > > >    extension is (just as with the command-line options).
> > >
> > > Why not use the standard boolean option semantics instead?
> > > ...
> > > Anyone? :)
> > 
> > I think it's a reasonable idea, but it may be "hard" to precisely match 
> > the boolean semantics (which permit all kinds of weird stuff); this 
> > section probably needs special parsing to allow arbitrary extension names
> > and not a fixed table of boolean variables.
> 
> That is correct, but I think it should be possible to emulate the
> boolean semantics, which should be fairly straightforward to change.

I got to this one tonight while waiting for a build to finish.  The
"Extensions" section of the config file now accepts all of the standard
boolean options (true/false, on/off, yes/no, 1/0).

Kevin