DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=23942>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=23942 Addition of a local property ------- Additional Comments From [EMAIL PROTECTED] 2004-10-21 17:45 ------- Matt, how many builds will that break? Notice that <A/> may have come from some other antlib and hence expects nothing about local scopes. It may be setting a property for some other macro in that antlib. On the other hand <b/> knows nothing about the private communication (implementation detail) between those macros. But it needs a local scope for its own properties. So even if there is no name collisions we break the code in <a/>. BTW, one of the problems I have with all this shadowing is that for a project to be correct now I need to know the details of the implementations of all the macros in use, because I may shadow by accident a name used by someone else. In some 3rd party antlib that I do not know about. Of course my proposal did not have that problem ;-) Although I recognized that name collisions were there already in ANT. Can that be solved with a scope ? Hummmm..... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
