For now, I would just hard code it. On 7/20/17, 12:55 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>Cool. So what would you recommend the convention to tell the compiler to >do so? A meta tag? a comment directive? (i.e. @debug) > >> On Jul 20, 2017, at 10:51 AM, Alex Harui <aha...@adobe.com.INVALID> >>wrote: >> >> I believe there is code that becomes part of the optimizer.jar that >> removes the trace statements. It might be possible extend that code to >> remove other things. >> >> -Alex >> >> On 7/19/17, 11:47 PM, "Harbs" <harbs.li...@gmail.com> wrote: >> >>> I don’t think there were any responses to this. >>> >>> As it stands, the debugging functions will exist in release versions of >>> swfs. >>> >>> Harbs >>> >>>> On Jul 16, 2017, at 12:07 PM, Harbs <harbs.li...@gmail.com> wrote: >>>> >>>> 1. The debugging functions should disappear in a release build of JS, >>>> but I’m not sure how to make the same thing happen in a release build >>>>of >>>> SWF. I don’t think a debug config is the solution, because the debug >>>> statements should be preserved in framework code and only be stripped >>>> out for application release builds. Does anyone have ideas on how to >>>>go >>>> about doing that? >>> >> >
