3 ms·
As long as * I can't write my own JIT compiler because of a lack of VirtualAlloc() and VirtualProtect() functions * I don't have access to some other lowlevel
by wolfgke 14y ago
As long as
* I can't write my own JIT compiler because of a lack of VirtualAlloc() and VirtualProtect() functions
* I don't have access to some other lowlevel functions not available in WinRT that exist in WinAPI
* I am forced to use Microsoft's App Store to provide my Metro applications
I am not in the slightest interested in writing applications for WinRT.
See http://www.freelists.org/post/luajit/FYI-No-JIT-on-Windows-8-for-ARM http://www.freelists.org/post/luajit/FYI-No-JIT-on-Windows-8... for explanations to the first point.
- pjmlp 14y agoIsn't C++, all .NET languages enough? Just use the tools the platform offers, instead of using the same hammer everywhere.
- wolfgke 14y agoI simply want to be able to build my own hammer if necessary. Microsoft - of course - does not have to build the hammer I want to use - but give me the possibilities to do so - in this case access to these API functions. The Javascript engine used for Metro applications (Chakra) also uses these API calls, so even Microsoft is (obviously) not able to relinquish using these API calls for writing a JIT compiler. So: I really only want to use the tools the platform offers - but in the same way Microsoft does; not in the limited way that Microsoft forces outside developers.
- deleted 14y ago[deleted]
- quotemstr 14y ago> lack of VirtualAlloc() and VirtualProtect() functions While these API not be in the "modern" SDK, the system calls behind them still work just fine. (They have to: otherwise, malloc wouldn't work.) You can walk ntdll's export table manually and find NtProtectVirtualMemory and friends. Also, SYSENTER is a thing.