Alan Cox <email@example.com>:
> Ok I see where you are going with that argument. However when you parse all
> the existing Config.in files into a tree you can see those properties by
> looking from any node back to its dependancies
Granted. If, that is, the representation you generate supports that kind
of backtracking. This turns out to be very hard if you're starting from
an imperative representation rather than a declarative one.
But, as a separate issue, the CML2 design *could* be reworked to support
a multiple-apex tree, if there were any advantage to doing so. I don't
see one. Do you?
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Good intentions will always be pleaded for every assumption of authority. It is hardly too strong to say that the Constitution was made to guard the people against the dangers of good intentions. There are men in all ages who mean to govern well, but they mean to govern. They promise to be good masters, but they mean to be masters. -- Daniel Webster - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.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 : Sun Apr 15 2001 - 21:00:17 EST