Re: Re: geant: notion of local variables

Indeed, I first used the wrong email address which is not registered on 
the list.
and I replied to my own message, because I thought my original message 
were delayed.

I guess it is somewhere in "wait to be approved"
Anyway, what matters is the second email with the patch.

I simply add  <setlocal name="..." value="..." />   (similar to <set /> 
task)
and I added  local_variable to task <available /> since most of the 
time, the result should be `local'
but to avoid breaking code, this is just a new task's attribute, and 
this is not the default.

I'd like to add :
* to any tasks, in the same way we have   <task  if="condition" />
<task  if_available="$resource" />  or simply <task  
available="$resource" />

* for copy, move and so on ...
        accept_errors and exit_code_variable  

* and of course ... the <group ../> task or entity

* even a <break .. />  to be able to exit a target before the end, but 
... this might not be a good idea

Any comments ?

But for now ... I am waiting for feedback on the addition of "local" 
variables

--Jocelyn

On 2/2/2008 14:22 PM, Eric Bezault wrote:
> Hi Jocelyn,
>
> Somehow I didn't receive the original message that you sent on
> January 31rst. I'm glad you copied it below. If Sven has no
> objection about this addition to geant, then I'm fine with it.
> Note that I didn't review your code below, but I guess that
> you know the code of geant better than I do these days.
>
> It has been a long time since we didn't hear from Sven in the
> Gobo mailing lists. Sven, are you still here?
>