On 1/10/17, 10:10 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>Hi Alex, Josh, > >as we MXML/AS3 is our domain, I think we should "unify" how it behaves. >That's the best way and the more coherent I can think... Another option is to have the compiler generate a warning or error if you use hasOwnProperty. Do you only use hasOwnProperty to try to see if a property changed? If so, I think it just won't work when you start using Object.defineProperty and I'm not sure how we'd be able to "unify" it. How would we know what the backing variable is for a property? Thoughts? -Alex
