Comments on: Variable Clashes http://jacksondunstan.com/articles/194 Mastering AS3 Mon, 14 May 2012 17:02:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: skyboy http://jacksondunstan.com/articles/194/comment-page-1#comment-1063 skyboy Sun, 24 Oct 2010 18:21:12 +0000 http://jacksondunstan.com/?p=194#comment-1063 There's another article a few further along (newer) where you copy/pasted the wrong code from someone's comment as well, but I don't recall which one; And I agree, this is most definitely a bug (as in another article you showed different types throw a warning/error), and should be reported. There’s another article a few further along (newer) where you copy/pasted the wrong code from someone’s comment as well, but I don’t recall which one; And I agree, this is most definitely a bug (as in another article you showed different types throw a warning/error), and should be reported.

]]> By: jackson http://jacksondunstan.com/articles/194/comment-page-1#comment-1049 jackson Sun, 24 Oct 2010 07:31:20 +0000 http://jacksondunstan.com/?p=194#comment-1049 Thanks for catching these! I've updated the article so the first example has the proper warning. It's been quite a while since I wrote this article, but I have no idea how I got the warning that was there. I've also updated the second example to include <code>arguments[0]</code>, as you suggest, since it is definitely a way to access the parameter. It's still a shame that the compiler behaves this way: it's absurd that there is no error or even warning and the generated program behavior is quite unexpected, at least to me. Thanks for catching these! I’ve updated the article so the first example has the proper warning. It’s been quite a while since I wrote this article, but I have no idea how I got the warning that was there. I’ve also updated the second example to include arguments[0], as you suggest, since it is definitely a way to access the parameter. It’s still a shame that the compiler behaves this way: it’s absurd that there is no error or even warning and the generated program behavior is quite unexpected, at least to me.

]]> By: skyboy http://jacksondunstan.com/articles/194/comment-page-1#comment-1048 skyboy Sun, 24 Oct 2010 06:32:46 +0000 http://jacksondunstan.com/?p=194#comment-1048 I don't fully understand your first example/warning pair. As for the second one, that's allowed because of the <code>arguments</code> variable, allowing you to access the argument <code>a</code> with <code>arguments[0]</code>. I don’t fully understand your first example/warning pair.

As for the second one, that’s allowed because of the arguments variable, allowing you to access the argument a with arguments[0].

]]>