Difference between revisions of "MorphOS API and Its Organization"

From MorphOS Library

(Let's start from the author's name...)
 
(Introduction. Sections.)
Line 1: Line 1:
 
''Grzegorz Kraszewski''
 
''Grzegorz Kraszewski''
 +
 +
 +
An Application Programmer Interface of an operating system consists of thousands of functions usually. MorphOS is no exception here. Its kernel is not monolithic however. The API is functionally (and physically) divided into libraries. Only a few largest libraries contain more than 50 functions. A core set of most important libraries is contained in the system boot image. The rest is placed on the system partition in ''MOSSYS:Libs'' (libraries delivered with the system) and ''SYS:Libs'' (third party libraries) directories. Disk based libraries are loaded on demand. All these libraries are shared, it means all processes using a library execute the same code loaded to memory once.
 +
 +
==Libraries Overview==
 +
 +
 +
==How to Use a Library in an Application==
 +
 +
 +
==Manual Library Opening and Closing==
 +
 +
 +
==Technical Insight==

Revision as of 16:30, 23 October 2010

Grzegorz Kraszewski


An Application Programmer Interface of an operating system consists of thousands of functions usually. MorphOS is no exception here. Its kernel is not monolithic however. The API is functionally (and physically) divided into libraries. Only a few largest libraries contain more than 50 functions. A core set of most important libraries is contained in the system boot image. The rest is placed on the system partition in MOSSYS:Libs (libraries delivered with the system) and SYS:Libs (third party libraries) directories. Disk based libraries are loaded on demand. All these libraries are shared, it means all processes using a library execute the same code loaded to memory once.

Libraries Overview

How to Use a Library in an Application

Manual Library Opening and Closing

Technical Insight