Eric,
I recently ran into a compiler bug (confirmed as such by MM) that is
very reminiscent of the problem you mention, in that the compiler breaks
in a full compile, but works in an incremental compile. (In my case,
the breakage consisted of emitting faulty property-binding code, rather
than failing with a compile error, so I think I had it worse than you in
that it wasn't even obvious that the compiler was broken :).
Another similarity between your problem and mine is that my bug was
triggered by a cyclic dependency of a kind, although in my case the
cycle was between an AS and an MXML file, and the references were just
mutual data type references, not component instances. (And come to
think of it, you don't actually have a cycle, as far as you can tell --
although have you looked in the generated AS to see if there is any
back-reference of any kind?)
So, FWIW, I was able to work around the problem in a way which you may
be able to adapt: I discovered that the compiler behavior is a function
of the static dependencies between various source files. Adding or
removing explicit references between classes/components can change the
behavior, presumably by changing the compilation order and the internal
context against which a source unit gets compiled.
A simple way to add an explicit compile-time dependency to a source file
is to use the latter's class as a data type:
var foo: ReferencedClass;
Hope this helps. I'll send you the reproduction info for my bug if you
want it.
. . . . ...j
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
