[ https://issues.apache.org/jira/browse/FLEX-33735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779883#comment-13779883 ] 

Sword Dragon commented on FLEX-33735:
-------------------------------------

I have another idea how this could be solved. Maybe the compiler could support pragmas so the user can disable specific warnings temporary in the source code. This would also provide a huge advantage from porting actionscript 2 code to actionscript 3 code on big projects as otherwise anybody will see during the complete porting process warnings that were already processed.
                
> Compiler warnings on runtime shared libraries if migration warnings are enabled
> -------------------------------------------------------------------------------
>
>                 Key: FLEX-33735
>                 URL: https://issues.apache.org/jira/browse/FLEX-33735
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: .Unspecified - Compiler
>    Affects Versions: Apache Flex 4.10.0
>         Environment: Linux 3.11 x86_64
>            Reporter: Sword Dragon
>            Priority: Trivial
>         Attachments: output.log
>
>
> Initially I have reported this issue on Adobe Flex 4.6 (https://bugs.adobe.com/jira/browse/SDK-32330) but it also exists in Apache Flex 4.10. If the migration warnings are enabled the runtime shared libraries will show some compiler warnings. In the attachments is an example output.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira