Difference between revisions of "Build your library"
m |
Hzwakenberg (talk | contribs) m |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category: |
+ | [[Category: Library]] |
| + | We're not going to give a course in architectural concepts here, but we'll give the details of how the Liberty Eiffel utilities can help you write high quality libraries. |
||
| + | The simplest case is that of a "100% Eiffel" library. In this case, Liberty Eiffel provides its compiler and its [[Library interface|standard library]], which already contains a rich variety of features. |
||
| − | We're not going to give a course in architectural concepts here, but we'll give the details of how the SmartEiffel utilities can help you write high quality libraries. |
||
| + | Liberty Eiffel also provides a documentation utility: [[eiffeldoc|eiffeldoc]]. |
||
| − | The simplest case is the case of a "100% Eiffel" library. In this case what SmartEiffel provides for you is its compiler and its [[Library interface|standard library]], which already contain a rich variety of features. |
||
| + | In certain cases, a library must be able to interface with the underlying system, to get access to low level functions. One can imagine, for example, creating an audio library (sorry, these days one says "multimedia"), to make system calls to access the sound card. |
||
| − | SmartEiffel also provides a documentation utility: [[eiffeldoc|eiffeldoc]]. |
||
| + | Liberty Eiffel provides a powerful utility: [[plugins]]. You can also use, even though it has been superseded, an older mechanism, [[externals|externals]]. |
||
| − | In certain cases, a library must be able to interface with the underlying system, to get access to low level functions. One can imagine, for example, creating an audio library (sorry, these days one says "multimedia"), to make system calls to access the sound card... |
||
| − | |||
| − | SmartEiffel now provides a powerful utility: [[plugins]]. You can also, even though it has been superseded, use an older mechanism, [[externals|externals]]. |
||
There are also two other mechanisms: [[inlining|inlining]] and [[cecil]]. |
There are also two other mechanisms: [[inlining|inlining]] and [[cecil]]. |
||
| + | |||
| + | For more in-depth background information about building reusable software components and libraries, check out reference "RS 1994" on the [[Bibliography]] page. |
||
Latest revision as of 13:16, 30 July 2024
We're not going to give a course in architectural concepts here, but we'll give the details of how the Liberty Eiffel utilities can help you write high quality libraries.
The simplest case is that of a "100% Eiffel" library. In this case, Liberty Eiffel provides its compiler and its standard library, which already contains a rich variety of features.
Liberty Eiffel also provides a documentation utility: eiffeldoc.
In certain cases, a library must be able to interface with the underlying system, to get access to low level functions. One can imagine, for example, creating an audio library (sorry, these days one says "multimedia"), to make system calls to access the sound card.
Liberty Eiffel provides a powerful utility: plugins. You can also use, even though it has been superseded, an older mechanism, externals.
There are also two other mechanisms: inlining and cecil.
For more in-depth background information about building reusable software components and libraries, check out reference "RS 1994" on the Bibliography page.