Jump to content
This is not recommended for shared computers
Sign in anonymously
Don't add me to the active users list
Banner advertising on our site currently available from just $5!
1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!
25 April 2015 - 04:13 PM
I've fixed this in revision 2160.
25 April 2015 - 09:02 AM
Thanks for reporting this.
I'll investigate and have it fixed as soon as possible.
18 April 2015 - 03:43 PM
The overhead of dynamically setting up the CPU registers that is necessary for calling the functions natively is quite similar to the overhead of the wrapper function.
Take a look at what goes on in the CallSystemFunction and you'll get a feeling of the overhead.
17 April 2015 - 01:40 PM
The calling convention doesn't influence the pre-compiled bytecode. As long as the script function signature is the same the bytecode will be compatible.
To wrap or not to wrap mostly depends on your own preference, unless of course you're building the application for a platform that does not yet have support for native calling convention.
For application functions that are called with a very high frequency it may be beneficial to try both wrapped and native to see which performs best on that platform.
13 April 2015 - 03:20 PM
Wow, two IDEs suddenly show up at the same time.
Options are always good.
GameDev.net™, the GameDev.net logo, and GDNet™ are trademarks of GameDev.net, LLC