That's almost like a dependency analysis pass within the class itself isn't
it? To rearrange the ordering, I mean.

Sounds like another fun iteration through test maintenance!

I might not get to that at this point, as I will be afk for a week or so on
a vacation with my kids.
I don't want to start anything I can't finish quickly before I leave, but
I'm happy to tackle stuff like that after I get back.

If I can see a quick solution to the above I might add it today, but
perhaps it is better to wait and try to figure out the bigger problem.

On Fri, Sep 30, 2016 at 11:12 AM, Alex Harui <aha...@adobe.com> wrote:

>
>
> On 9/29/16, 3:06 PM, "Greg Dove" <greg.d...@gmail.com> wrote:
>
> >it might be to do with the order of output I think.
> >Perhaps it is calling the bindable setter within the constructor but it is
> >not yet defined. Maybe this could also be covered by setting the private
> >backing var if inside the constructor for a bindable field.
> >
> >I can try to repro this later today and see if that is what is happening,
> >if so I will try to figure out a solution.
>
> I don't remember if there is a JIRA for this, but there are some issues
> with the way static initializers get run so if you do run into something
> like that, it might be time to solve the general static initializer
> problem.
>
> -Alex
>
>

Reply via email to