Structs can't be passed as reference.

[coconParticipant]

It looks like structs can’t be passed as reference, is it possible?

Monkey

#Import "<mojo>" Using mojo.. Struct TypeStruct Field Test:String End Class TypeClass Field Test:String Method ToString:String() Return Test End End Class TypeChanger Method Set(t:TypeStruct) t.Test = "Set" End Method Set(t:TypeClass) t.Test = "Set" End End Function Main() New AppInstance Local t1 := New TypeStruct Local t2 := New TypeClass Local tc := New TypeChanger tc.Set(t1) tc.Set(t2) Print(t1.Test) Print(t2.Test) End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

#Import "<mojo>" Using mojo..   Struct TypeStruct Field Test:String End   Class TypeClass Field Test:String Method ToString:String() Return Test End End   Class TypeChanger Method Set(t:TypeStruct) t.Test = "Set" End Method Set(t:TypeClass) t.Test = "Set" End End   Function Main() New AppInstance   Local t1 := New TypeStruct Local t2 := New TypeClass Local tc := New TypeChanger tc.Set(t1) tc.Set(t2) Print(t1.Test) Print(t2.Test) End

[Mark SiblyKeymaster]

In general, no.

You can Varptr a struct use a pointer, but this is very unsafe.

[arpieParticipant]

Mark, would you mind quickly clarifying why this would be very unsafe?  Is it for the usual reasons that pointers are unsafe or is there something more dangerous about Varptr and Ptr in Monkey?

[coconParticipant]

The catch here is when you want to use a library written in C through a module, you might use pointers to call the C API (for example the OpenGL API), personally I would no find something odd about this approach.

[Author]

Posts