> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > > Because if that is the case, maybe we can solve the problem in a > > completely different way, which is specific to <macrodef/>. > > What you describe is pretty much what I (and probably anybody > else) use as a workaround. I create what would be a local > property by using a name contains the name of at least one of > the task's attributes. > > I don't think I'd like to turn this into a formalized > solution with the property namespace polution you get. Also, > you can't guarantee unique property names since you don't > know which normal Ant property names will be used later in > the build - outside of <macrodef>s. All you could guarantee > is that the name hasn't been used yet and won't clash with a > name a <let> construct would create later. >
True, but I doubt many people will use properties called for example: "#ant.task.macrodef.example.let####1" "#ant.task.macrodef.example.let####2" "#ant.task.macrodef.example.let####3" "#ant.task.macrodef.example.let####4" Or some silly name space like that. My problem with the real local properties is that I think they will require a lot of work and thought before we can have something really rubust. If, as we have done in the past, put out there something that we have not really considered all the concequences properly, we will finish with all sorts of backward compatibility issues when we find the drawbacks (or the users find them). It would not be the first time this happens so I am talking based on the historical experience. The payoff of general local properties seems quite limited, as far as I can see. Have you found any compelling usage for them on their own? <ant> & co. already provide stack (but is expensive). Whatever we do in this regard, we probably need to provide for references also. But he, I just though about this for 30secs before proposing it, so shoot at it if you think is not worth the electrons is written on :-) Jose Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
