Thursday 15 April 2010

System call library -


How practical would it be to implement a "integrated" system call library? Such a library would have a cover for the actual system call of the OS. In this way, you can write a code using "Unified System Call Library", and then the library will handle you in creating the same OS-specific calls (you will have to make a separate version of the library for each OS). This will allow easy creation of portable applications.

I think this is alcohol, but alcohol is just on Linux to run windows applications.

Has it been done already?

Edit:

Or, allows you to run any compatible application. Better yet, use an existing popular standard (POSIX?) And make wrappers for windows, Mac, etc. OS calls, so that any POSICs app can run on those related operating systems.

Double Edit:

After a few ideas, I realized that it already has many libraries. But for some reason, some calls start dropping (otherwise why are not all the applications portable for the OS portable?)

< P> Sure, the purpose of Pozx is to unify the operating system, in particular, there is a chapter about C Functions. Under Linux, BSD, and * NIIX make conformance with Gibbic Pauses. Under Windows you need to install Sigwin. If you write programs according to POSX standard, then they will run under Linux + Gribbick, Windows + Signin etc. ... Unfortunately, Pozzx does not define communication with hardware. Communication with hardware is unequal and depends on the type of operating system and hardware.

No comments:

Post a Comment