Cannot use function in Super.New() method

[blitz-research]

Cannot use function in Super.New() method

[blitz-research]

No, MAV's aren't intended behaviour!

Should be fixed now.

[blitz-research]

Have you done an updatemx2cc?

On Sun, Sep 11, 2016 at 7:49 PM, Wiebo de Wit [email protected]
wrote:

I assume the fix has not been uploaded yet, as the problem is still there.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#39 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADU3QhwAhfk0z9gW_sVNJtQRmWjJv5F3ks5qo7J3gaJpZM4JVRbK
.

[blitz-research]

Yay!

Yeah, only 'tagged' releases have prebuilt binaries in them.

It's tricky to add updatemx2cc to rebuildall, as depending on what I've
been playing with you either need to build modules first or mx2cc.

Should add this to the readme...

On Sun, Sep 11, 2016 at 8:41 PM, Wiebo de Wit [email protected]
wrote:

Apparently updateall.sh does not update mx2cc? I performed the update as
you suggested and now it's compiling and running!!! Thanks.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#39 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADU3Qjmfupw_IA5Wf1AZaROMCGmmdAwjks5qo761gaJpZM4JVRbK
.

[wiebow]

Is this intended behaviour @blitz-research ?

[wiebow]

@blitz-research , I assume the fix has not been uploaded yet, as the problem is still there.

[blitz-research]

...and if it's still happening can you post some runnable code? I threw
something together for testing that works, but it may not be the same...

On Sun, Sep 11, 2016 at 8:31 PM, Mark Sibly [email protected] wrote:

Have you done an updatemx2cc?

On Sun, Sep 11, 2016 at 7:49 PM, Wiebo de Wit [email protected]
wrote:

I assume the fix has not been uploaded yet, as the problem is still there.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#39 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADU3QhwAhfk0z9gW_sVNJtQRmWjJv5F3ks5qo7J3gaJpZM4JVRbK
.

[blitz-research]

Here's the sample I used, which used to crash like crazy...

Class T
Field str:String
Method New( str:String )
Self.str=str
Print "T.New("+str+")"
End
End

Function F:T( str:String )
Return New T( str )
End

Class C

Method New( t:T )
Print "Here! t.str="+t.str
End
End
Class D Extends C

Method New( str:String )
Super.New( F( str ) )
End
End

Function Main()

New D( "Hello!" )
End

On Sun, Sep 11, 2016 at 8:32 PM, Mark Sibly [email protected] wrote:

...and if it's still happening can you post some runnable code? I threw
something together for testing that works, but it may not be the same...

On Sun, Sep 11, 2016 at 8:31 PM, Mark Sibly [email protected] wrote:

Have you done an updatemx2cc?

On Sun, Sep 11, 2016 at 7:49 PM, Wiebo de Wit [email protected]
wrote:

I assume the fix has not been uploaded yet, as the problem is still
there.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#39 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADU3QhwAhfk0z9gW_sVNJtQRmWjJv5F3ks5qo7J3gaJpZM4JVRbK
.

[wiebow]

Apparently updateall.sh does not update mx2cc? I performed the update as you suggested and now it's compiling and running!!! Thanks.

This allows me to get of a lot of workaround code in object creation etc...