On Wed, Jan 30, 2002 at 08:54:44AM +0100, Patrick Mauritz wrote:
> short being between now and the cml2 inclusion?
CML2 is butt-ugly to read and maintain, at least for drivers. It is
my hope that Eric will take input that will make CML2 more readable
and useable by kernel hackers.
The current config language, for all the flaws CML2 proponents love to
point out, is quite readable and understandable. It doesn't force
the entire domain of CONFIG_xxx symbols on you, like CML2 does.
[Unless this has changed recently] CML2 forces architecture X to be
mindful of changes in architecture Y. For some tasks this make sense,
but for other cases this is a completely needless usurpation of an
architecture's control of the CONFIG_xxx namespace. The current
config language allows an arch to -control- the namespace, while
CML2 appears to reduce flexibility by requiring global instead of
arch-specific control of the namespace.
It is my hope that some sort of compromise can be found... :(
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jan 31 2002 - 21:01:15 EST