Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [FalconJX]trace statements
From: Harbs <harbs.lists@gmail.com>
In-Reply-To: <D3503C40.692F4%aharui@adobe.com>
Date: Thu, 5 May 2016 10:02:34 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <100677EE-E9F8-473D-B043-BE2D04A85C3A@gmail.com>
References: <186CDB21-B0B0-41BD-8C92-AFC47B0F690C@gmail.com> <D35030EF.692E7%aharui@adobe.com> <34F7ADB9-A200-4454-A15E-6671285695AE@gmail.com> <D3503C40.692F4%aharui@adobe.com>
To: dev@flex.apache.org
archived-at: Thu, 05 May 2016 07:02:41 -0000

Done: https://issues.apache.org/jira/browse/FLEX-35087

On May 5, 2016, at 9:55 AM, Alex Harui <aharui@adobe.com> wrote:

>=20
>=20
> On 5/4/16, 11:47 PM, "Harbs" <harbs.lists@gmail.com> wrote:
>=20
>> I was talking about removing the call to trace.
>>=20
>> I guess it really doesn=92t matter if the trace statements are there =
and
>> don=92t do anything except for making the download size of the code a =
bit
>> larger.
>>=20
>> How does it work in Flash? I've just assumed the statements are =
removed
>> completely.
>=20
> I'd have to double check, but I believe there is an optimizer class =
that
> removes the calls.  We could do the something like that in FalconJX.  =
File
> a bug so we don't forget about it.
>=20
> -Alex
>=20