Tag Info

New answers tagged


At least according to a quick web search, the expression "Linux ready" does not appear to be some sort of official designation for Swift projects. It looks like only Zewo uses it in that context. According to the project's README.md, it simply means that the project should work under Linux once a Swift implementation is available for Linux: Features: ...


Linux-ready implies that the project does not contain Apple Foundation frameworks, which would make the project platform specific. Once Apple releases their Swift compiler for Linux - which they announced will be by years end - Linux-ready projects should run "out of the box" on Linux.


of course it is. a notable example is "Out of this World". there's versions of that game for dos, os/2, windows, mac, snes, sega, playstation, nds, linux, android...pretty much anything! and it does that with very little change. that's because at its core it runs on its very own self contained sandbox. --quite a feat for its age. all the input/output is ...


The one major difference between coding in ASM on Win/Linux/OSX is the calling convention. There isn't one more difficult to use than the other, they're just different. You also need to be careful about the register that need to be preserved between calls. WINDOWS: RCX, RDX, R8, R9 The Microsoft x64 calling convention is followed on Windows and ...


Define an environment variable LD_PRELOAD to point to a shared library overriding required functions. See http://hackerboss.com/overriding-system-functions-for-fun-and-profit/


Once upon a time (80386 era) most computers had less than 16 MiB of RAM, there were no memory mapped PCI devices, and 1 GiB of space sounded insanely huge (especially for a "temporary kernel" that was only expected to be used until GNU finished their own kernel). Mapping all of the physical RAM into kernel space sounded like a good idea; so that's what ...


Linux Mutexes can be used for cross process synchronization. Been there, done that, very useful. The Mutex must be accessible to the processes concerned, such as being in a shared memory block. The Mutex could also not be shared, and therefore private to the process that created it. The Mutex functionality in Linux is not limited. Windows Mutexes are ...

Top 50 recent answers are included