AW: local properties
joking or a mixture? dimlet, define-my, local-var, ... or a very personal thing: the class is not typedef´d and the user can choose or we use something like the-type-which-introduces-the-local-only-available-of-properties-which-are-n ot-available-from-a-different-scope and the user uses a presetdef for getting the name ... /joking Jan -Ursprüngliche Nachricht- Von: Stefan Bodewig [mailto:[EMAIL PROTECTED] Gesendet am: Dienstag, 11. Januar 2005 13:58 An: [EMAIL PROTECTED] Betreff: Re: local properties On Tue, 11 Jan 2005, Kev Jackson [EMAIL PROTECTED] wrote: Sounds good, but is it possible to get a different name than let ? Peter Following the VBness of let, how about dim? ;) Actually it's a Lispness - for those of us who liked the name let, at least 8-) Hmm, borrowing from Emacs lisp, defvar? define-property? Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: local properties
target name=example
let
localproperty name=prop value=a local value/
echoprop is ${prop}/echo
/let
echoprop is ${prop}/echo
/target
should result in?
[echo] prop is a local value
[echo] prop is ${prop}
So, Task, Target, Parallel do not get changed.
I also think that the nested localproperty for the macrodef
task can be dropped initially. It would be easier to explain just one
container for local properties/
macrodef name=test
sequential
localproperty name=prop value=a local value/
echoprop is ${prop}/echo
/sequential
/macrodef
test/
echoprop is ${prop}/echo
result should be the same:
[echo] prop is a local value
[echo] prop is ${prop}
or do you want to something like
macrodef name=test
let
localproperty name=prop value=a local value/
echoprop is ${prop}/echo
/let
/macrodef
or
macrodef name=test
sequential
let
localproperty name=prop value=a local value/
echoprop is ${prop}/echo
/let
/sequential
/macrodef
Jan
Re: AW: local properties
[EMAIL PROTECTED] wrote:
target name=example
let
localproperty name=prop value=a local value/
echoprop is ${prop}/echo
/let
echoprop is ${prop}/echo
/target
should result in?
[echo] prop is a local value
[echo] prop is ${prop}
Yes.
So, Task, Target, Parallel do not get changed.
I also think that the nested localproperty for the macrodef
task can be dropped initially. It would be easier to explain just one
container for local properties/
macrodef name=test
sequential
localproperty name=prop value=a local value/
echoprop is ${prop}/echo
/sequential
/macrodef
test/
echoprop is ${prop}/echo
result should be the same:
[echo] prop is a local value
[echo] prop is ${prop}
or do you want to something like
macrodef name=test
let
localproperty name=prop value=a local value/
echoprop is ${prop}/echo
/let
/macrodef
No
or
macrodef name=test
sequential
let
localproperty name=prop value=a local value/
echoprop is ${prop}/echo
/let
/sequential
/macrodef
Yes, This is the case.
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: local properties
[edited for length] --- Peter Reilly [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: local prefix=tmp/ loadproperties prefix=tmp/ I do not see how it would be useful or how to implement it. :-) I think it could be useful. I don't remember how your local impl was structured, but there might be room for this as well. -Matt ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: local properties
Havent got an answer to that proposal: local prefix=tmp/ loadproperties prefix=tmp/ I do not see how it would be useful You could use all other tasks as they are. Many tasks store their result in properties. Some (like loadproperties) in multiple props. or how to implement it. :-) - Register the tmp as temporary prefix on Project - setNewProperty() (and the other *Propert* methods) check against the list of temporary props and allow overriding. - Project.deleteProperties(String prefix) would unset all properties with the registered prefix and deregister that. Just a quick idea ... Jan
AW: local properties
Sorry about not knowing the whole story :)
But could that be possible/usefule?
macrodef name=test
local prefix=tmp/
sequential
property name=tmp.test value=hello/
echo${tmp.test}/echo
/sequential
/macrodef
test/
echo${tmp.test}/echo
[test] hello -- from macrodef
[echo] ${tmp.test} -- outside macrodef, prop is unset
Jan
-Ursprüngliche Nachricht-
Von: Peter Reilly [mailto:[EMAIL PROTECTED]
Gesendet am: Freitag, 8. Oktober 2004 17:38
An: Ant Developers List
Betreff: Re: local properties
Jose Alberto Fernandez wrote:
Peter,
I just posted something on bug 23942 about a different approach
to this issue that I implemented on my machine at home.
It is a very small addition to macro and it does not require
any changes to the ANT machinery. I think everything we want
to be able to do in macros can be done this way.
Yes I have seen it.
I do not like it, - the [EMAIL PROTECTED] syntax is a bit ikky ;-)
However, it does solve the macrodef use case so if people
go for it, I would have no objection.!
Peter
The full implementation provides some additional features to
help you control the scope of let/ on antcalls and such
but all is based on the current machinery. No changes to CORE at all.
If you allow me to post it, or if you look at the example, you can
get a flavor for it.
You should place this as an attachment to the local buzilla report
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
