Hi Harbs,
I've added in your ticket affected version. Correct me if I did mistake.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FalconJX-trace-statements-tp52785p52796.html
Sent from the Apache Flex
Done: https://issues.apache.org/jira/browse/FLEX-35087
On May 5, 2016, at 9:55 AM, Alex Harui wrote:
>
>
> On 5/4/16, 11:47 PM, "Harbs" wrote:
>
>> I was talking about removing the call to trace.
>>
>> I guess it really doesn’t matter if the trace statements are there and
>> don’t do anythi
On 5/4/16, 11:47 PM, "Harbs" wrote:
>I was talking about removing the call to trace.
>
>I guess it really doesn’t matter if the trace statements are there and
>don’t do anything except for making the download size of the code a bit
>larger.
>
>How does it work in Flash? I've just assumed the st
I was talking about removing the call to trace.
I guess it really doesn’t matter if the trace statements are there and don’t do
anything except for making the download size of the code a bit larger.
How does it work in Flash? I've just assumed the statements are removed
completely.
On May 5, 2
On 5/4/16, 10:49 PM, "Harbs" wrote:
>Currently, trace statements are preserved and output to the console even
>in “release” builds of js.
>
>How hard would it be to have the compiler strip out trace statements when
>it does the minifying step?
Do you just not want the output to go to the conso