On 12/19/12 2:40 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:

> Hi,
> 
>> I don't think that's the right change.  I'm guessing the intent is to change
>> a local variable, not the instance's height property?
> 
> 
> Nice catch. Calling a variable the same as a local property is probably a bad
> idea. Best fix here I think would be to rename height to something else?
It isn't my favorite practice, but it shouldn't cause a compiler error or
warning.  It would be great if Chema could put together a simple test case
or unit test for this scenario.  We do frequently mask instance properties
with constructor arguments although that isn't quite the same thing here.


-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Reply via email to