On 02/06/2017 06:51 PM, Vít Ondruch wrote:
Dne 6.2.2017 v 16:00 Panu Matilainen napsal(a):
One open question I have is what to do with %undefine's: currently rpm
allows %undefining anything from any scope, and that is at odds with
any attempt to rationalize and formalize the scoping to something
actually comprehensible. A simple approach is that you can only
undefine something from your local scope or the global scope. But what
if there's something by the same name in between?
What is wrong with this? You always undefine the value from the top of
the stack ...
What do you mean by "this" - the current behavior or the alleged scoping
aware new version?
The current behavior indeed just removes from top of the stack with no
consideration as to who defined the macro and where. And this in a
system that makes claims about scoping...
- Panu -
_______________________________________________
Rpm-ecosystem mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-ecosystem
