Why use a standardized OS interface?

Using a standardized OS interface architecture will

Reduce the learning curve associated with adopting a new OS by using intuitive, flexible and standard APIs across multiple operating systems
Protect software investment by enabling efficient software re-use across multiple platforms
Eliminate manual updates to applications when upgrading to newer versions of OS

Related Articles
Why use a standardized OS interface?
Using a standardized OS interface architecture will
Why should I use OS Abstractor with my proprietary OS?
Using OS Abstractor with your proprietary OS will give you the following benefits: Leverage re-usable open source POSIX/Linux code to efficiently add feature rich services in a cost-effective to your proprietary OS Make your application more ...
OS Abstractor document says that we can use target OS native IO functions if I set MAP_OS_ANSI_IO to OS_FALSE. Does this mean that I can also call other target OS APIs from application program?
You should be able to use any native APIs directly from the target OS (as long as the API names are not the same).
OS Abstractor document says that we can use target OS native IO functions if I set MAP_OS_ANSI_IO to OS_FALSE. Does this mean that I can also call other target OS APIs from application program?
You should be able to use any native APIs directly from the target OS (as long as the API names are not the same).
Can OS Abstractor and Interface libraries be built as shared libraries? What about as DLLs?
OS Abstractor and Interface libraries can be built as shared libraries. This would be the recommended option if you develop multi-process applications. As far as DLL, the current release does not support this feature. However, MapuSoft can provide ...

Related Articles