I just took a look at UIDUtil.
If I dump Core.SWC, the UIDUtil.js in there has the following:
goog.provide('org.apache.flex.utils.UIDUtil');
/* FlexJS Static Dependency List: org.apache.flex.utils.BinaryData*/
goog.require('org.apache.flex.utils.BinaryData');
goog.require('org.apache.flex.utils.
> On Apr 9, 2017, at 12:50 AM, Alex Harui wrote:
>
> I assume this is only a problem for folks using -remove-circulars?
>
I have not tested with remove-circulars truned off, so very possibly, yes.
> I assume what is broken is the order of loaded files instead of something
> else?
Correct. Wit
I assume this is only a problem for folks using -remove-circulars?
I assume what is broken is the order of loaded files instead of something
else?
Thanks,
-Alex
On 4/8/17, 9:46 PM, "Harbs" wrote:
>Related issue:
>
>The recent changes to Falcon has broken UIDUtil which has the following:
>priva
Related issue:
The recent changes to Falcon has broken UIDUtil which has the following:
private static const UIDBuffer:BinaryData = new BinaryData();
Unless something changes, this needs to be changed to a getter.
> On Apr 8, 2017, at 11:40 PM, Harbs wrote:
>
> Currently initializing non-primi
Please provide some examples.
On 4/8/17, 8:40 PM, "Harbs" wrote:
>Currently initializing non-primitive static types are a big no-no in
>FlexJS. It causes all kinds of javascript runtime errors due to
>non-defined types depending on the order of loaded files.
>
>I think this is an area which need
Currently initializing non-primitive static types are a big no-no in FlexJS. It
causes all kinds of javascript runtime errors due to non-defined types
depending on the order of loaded files.
I think this is an area which needs some improvement. The improvement can take
two variations:
1. We ca
