I get this bug when I use constants as default parameters and want to work around it somehow without having to use literals. Annoyingly, they deffered the bug resolution and I could not find a satisfying solution to this. I suspect an incorrect compile order to be responsible for this issue and think there must be a way to influence it, preferably via compiler options, maybe with a more or less ugly hack.
My idea is to somehow force the compiler to compile the class with the constants that cause the error first, before anything else gets compiled. But I've no idea how to achieve this. So:
Is there any way to influence the compile order of the Flex MXMLC?
Moving constants definition in separate SWC might help.