Inconsistent inline behaviour. Can cause Null Object Reference about hxcpp HOT 4 CLOSED

This is most likely due to a bug in haxe codebase, please cross post in Haxe issues so we can fix it for 3.1.2

from hxcpp.

This is already fixed - but will need a new haxe (std libs) release to fix.

Hugh

On Fri, Mar 21, 2014 at 4:26 PM, Nicolas Cannasse
[email protected]:

This is most likely due to a bug in haxe codebase, please cross post in
Haxe issues so we can fix it for 3.1.2

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-38256514
.

from hxcpp.

Sorry - I was thinking of another bug.
This one looks like the re-orderer. We have seen a couple of bugs here
(there is a reason why it was on my bug list for many years) - maybe have a
flag to make it optional so we can "get out of trouble" if required.

Hugh

On Fri, Mar 21, 2014 at 4:29 PM, Hugh Sanderson [email protected] wrote:

This is already fixed - but will need a new haxe (std libs) release to fix.

Hugh

On Fri, Mar 21, 2014 at 4:26 PM, Nicolas Cannasse <
[email protected]> wrote:

This is most likely due to a bug in haxe codebase, please cross post in
Haxe issues so we can fix it for 3.1.2

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-38256514
.

from hxcpp.

We're already supposed to be dealing with the short-circuit situation, but apparently there's disagreement within the compiler about what constitutes a side-effect. I'll clean that up a bit.

Unfortunately I can't execute the hxcpp unit tests at the moment because they simply crash on me. I'll try to debug that later and rely on travis for now.

from hxcpp.