Keith Owens <[EMAIL PROTECTED]>:
> IMHO the only correct method is to write out only the visible symbols.
The current logic looks like this:
1. If the symbol has been explicitly set, write it out.
2. Otherwise, if the symbol's visibility predicate is all frozen symbols and is n,
suppress it.
3. Otherwise, if an ancestor symbol is n, suppress it.
4. Otherwise write it out.
Am I being too complicated here?
> Also I suspect that part of the CML2 problem is inconsistent state
> about which symbols are visible or not, caused by the slightly
> different constraints of the front ends. If that is the case, the fix
> is obvious.
The front ends all use the same rulebase, so they're deducing from the
same constraints. And they all use the same is_visible() predicate.
> Once an acceptable config has been entered and has passed all the
> rules, delete all visibility state from the config and recalculate the
> visbility state of each symbol from scratch. That is probably the only
> way to guarantee identical output irrespective of front end variations.
There is no visibility state to delete. Visibility is recomputed every time,
so this is the way it's done now.
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
"I hold it, that a little rebellion, now and then, is a good thing, and as
necessary in the political world as storms in the physical."
-- Thomas Jefferson, Letter to James Madison, January 30, 1787
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
