Funniest Flex (beta4) compiler error
This is a quick one
Quote:
1067: Implicit coercion of a value of type flash.display:InteractiveObject to an unrelated type flash.display:InteractiveObject.
Unfortunately, I was not able to reproduce it to file a bug. Just restarted Flash Builder and it was gone.
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
October 8th, 2009 at 3:22 pm
That can happen.
That sort of weird error happens when a class is compiled into two separate ApplicationDomains, and is then passed from one ApplicationDomain to another.
The two classes are _called_ the same thing, but are implemented in different bits of (sometimes identical) code; so the Flash Player thinks they’re different classes.
October 8th, 2009 at 3:48 pm
I’m afraid you didn’t pay attention (to the very short post above). This message was issued by Flex compiler, not by the runtime.
And it’s not just funny, it’s perplexing.
October 8th, 2009 at 4:46 pm
very funny and confusing indeed
October 8th, 2009 at 5:27 pm
Where…? Ah, in the title.
Fair enough. I was only trying to be helpful in case it crops up again. The situation I describe has puzzled a number of people in the past.
Consider the comment withdrawn.
October 8th, 2009 at 6:08 pm
Sure, thank you. The situation you described is common for me as I work allot with disconnected ApplicationDomains.
For sure, your comment will help people that land in this page searching for a solution to the problem you mentioned.
October 9th, 2009 at 6:54 am
Something similar has happened to me and I nailed it down to the Eclipse Java compiler getting overflowed.
When I closed and opened the Builder, everything was compiling fine and no errors produced.