Hi Brad, Michael,
Your explanation makes sense. I hadn't run into this problem before, and
assumed I could safely access ARGVn, whether or not n >= ARGC. Turns out
I was just lucky. I'll use ARGN instead.
Thanks,
Marcel Loose.
On Fri, 2009-11-13 at 07:52 -0500, Brad King wrote:
> Michael Wild wr
Michael Wild wrote:
Looks like the scoping algorithm only "overwrites" these automatic
variables only if they are associated with actual arguments, otherwise
it just inherits them. Same thing happens if my_macro is a function.
Smells like bug to me ;-)
It's behaving exactly as documented. Fu
On 13. Nov, 2009, at 12:33 , Marcel Loose wrote:
Hi all,
I've been bitten by an IMHO weird behaviour with argument
substitution.
When I call a macro from within a function, then unused ARGVn
variables
(where n=1..9) retain the value that they got when entering the
function. Is this a bug?
Hi all,
I've been bitten by an IMHO weird behaviour with argument substitution.
When I call a macro from within a function, then unused ARGVn variables
(where n=1..9) retain the value that they got when entering the
function. Is this a bug?!
This example demonstrates what I mean:
$ cat ../CMakeL
