Hello. Thanks for your response.

> not *all* options are defopt'ed.  indeed, if you were to add one, that
> would not be defopt'ed.  it is because of this that the make clean is
> recommended.

Ah, so it is possible to add anything I want to options and it will be
passed to the compiler as defines, isn't it so?! 

In this case I would propose that config issues a warning every time it
encounters an option which is not defopt'ed. This would catch possible
typos when editing the config file (otherwise, you make a typo in an
option which is defopt'ed and it is silently passed as a define and
won't do anything (in the better of cases) and you don't have a way do
detect it quickly).

It would also possibly remind developers to defopt their new options.

Does this proposal sound reasonable?

> 
> note, however, that if you're not changing options all that much, or
> you're only changing ones that you found in the GENERIC config file,
> you're probably okay.

Ah. So all the options in GENERIC are defopt'ed? Can this be said about
all the options listed in options(4) man page?

I think config(8) and/or options(4) man page should mention in what
cases should "make clean" be done.

Currently, options(4) says: 

Note: Options are passed to the compile process as -D flags to the C
compiler.

and doesn't mention defopt'ed options at all.

Bye	Pavel