Re: Target specific contents of variables

Lars Ivar Igesund wrote:

> I have a recipe with several programs and a lib. By accident, I found 
> out that if I wanted to set DEBUG for only one of the programs, I had to 
> set it for both the program name and the file, like this:
> 
> :program foo { var_DEBUG = yes } : foo.d { var_DEBUG = yes}
> 
> This is necessary because correct debugging is dependent on using the 
> correct switches in both the compile and link phases. Leaving out one of 
> the attribute blocks, removes the correct flag for that phase. I would 
> possibly expect
> 
> :program { var_DEBUG = yes} foo : foo.d
> 
> to work, but the DEBUG wasn't set for either action.
> 
> It doesn't really matter, since I was able to use the global DEBUG, but 
> I think it should be possible (wasn't a similar problem discussed recently?)

Sounds like a good idea.

The use of attributes for a command isn't entirely consistent.  Perhaps
we should make it a rule that when the attribute is given directly after
the command name it applies to the whole command.  When it is given
after an argument it applies to the argument.  That makes sense, doesn't
it?

-- 
hundred-and-one symptoms of being an internet addict:
144. You eagerly await the update of the "Cool Site of the Day."

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html ///


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285