Forum Replies Created
-
AuthorPosts
-
But can we have type info for simple pointers, array…?
Still not sure what you mean – this works (as per docs):
Monkey12345Print Typeof< Int[] >Local p:Int PtrPrint Typeof( p )What are you trying to do is the 64k Q?
Nice!
Arrays are not copied automatically, ie: they are reference types.
There is no built-in way to do this yet (it’s easy for ‘2’ or ‘3’ dimensions, harder for ‘N’!) but abakobo’s solution look cool, although I’d probably rename it to Copy2DArray.
Have you looked at the reflection section in the language manual? This shows the correct use of TypeOf and TypeInfo.
(you may need to grab the latest github develop branch, this may have only recently been added).
I did this experiment and I see that I can’t mutate the element of the list directly, however I can mutate the local copy. Is this behavior valid or not?
Yes, because structs are always passed ‘by value’ (ie: copied), so this line…
Local item := list.FirstNode().Value
…copies FirstNode().Value to item.
One way to deal with thinking about this stuff is to mentally replace ‘some struct type’ with, say, ‘int’ (also a struct type) in which case you’ve simply got a list of Ints, and hopefully it’s clear that…
Local item := list.FirstNode().Value
…will set item to a *copy* of FirstNode().Value as, like all struct types, ints are copied when passed to functions, returned from functions or assigned to variables.
textView.MakeKeyView()
Have a look in the modules/mojox/tests folder for some mojox examples.
textView.MakeKeyView()
Have a look in the modules/mojox/tests folder for some mojox examples.
No, cxx2mx2 is not functional and probably never will be. I should really remove it…
I had it ‘sort of’ working with chunks of bullet, but realized it was all becoming super bullet-specific (and even bullet wasn’t following its own conventions all the time) and eventually went back to hand converting stuff as necessary.
So cxx2mx2 is dead for now as c++ is (for me anyway) just too hard to convert via automation.
June 21, 2017 at 10:27 pm in reply to: Which NDK version should be used for the Android target? #8854You first need to install the NDK from android studio, and then make sure monkey2 can ‘see’ it, either by adding the dir ndk-build is in to your PATH, or modifing this line in bin\env_windows.txt
PATH=D:\devtools\Android\sdk\ndk-bundle;${PATH}
Actually, I recommend using the current instructions in the monkey2 manual:
Monkey2 uses the emscripten sdk compilers and tools to build emscripten and wasm apps.
To install the emscripten sdk, please see this page: https://github.com/juj/emsdk/blob/master/README.md.
After installation, you should have em++ 1.37.9 installed. Use ’em++ -v’ to check version.
Emscripten is still kinda in flux and is unlikely to be ‘fun’ to get going for a while yet!
when I upload to the website the old cashed version loads and not the new.
This is likely to be a webserver issue I think, eg: there may be some apache config settings for cache control?
No idea what’s up, all is working OK here – anyone else these problems?
What version of emscripten are you running? I’m on 1.37.9, use ’em++ -v’ to find out.
Use this link to grab installer for 1.37.9, there’s another one around that installs an older version I think…
https://github.com/juj/emsdk/blob/master/README.md
Are you using mserver to host/run it?
-
AuthorPosts