Re: [jamboost] variable changing values unexpectedly

From: Matt P. (matt_at_[hidden])
Date: 2003-12-08 04:33:12

Thank you for your response.

I did find, like you suggested, that the rule ProcessXML changes the
variable because it uses the same variable name:

rule ProcessXML
{
NotFile $(1) $(2) $(3)
for gOUTPUT_XML in $(2)
{
....

Isn't gOUTPUT_XML declared local when it's part of that for loop, or do
I have to (can I?) declare it local:

for local gOUTPUT_XML in $(2)

Thanks,

Matt

> > echo "3" $(gOUTPUT_XML) ;
> >
> > ProcessXML xml : $(gOUTPUT_XML) : $(CX_MAIN) ;
> >
> > echo "4" $(gOUTPUT_XML) ;
> 
> > The question, well, ok, I have two questions:
> > 1- Why is the value of gOUTPUT_XML changing from step 3 to step 4?
> 
> It's hard to tell. Probably, ProcessXML changes it?
> 
> > 2- Why is there two passes at this Jamfile?
> 
> In V1, all Jamfiles are processed twice. If some code can't work twice, you 
> can wrap it in 
> 
> if ! $(gIN_LIB_INCLUDE) {
> }
> 
> - Volodya
> 
> 
> 
> 
> To unsubscribe from this group, send an email to:
> jamboost-unsubscribe_at_[hidden]
> 
> 
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
> 
> 
>