dido:public:ra:1.4_req:1_func:platform:sw_arch
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:1_func:platform:sw_arch [2021/08/13 11:56] murphy |
dido:public:ra:1.4_req:1_func:platform:sw_arch [2021/08/18 10:41] (current) murphy [About] |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| Runtime libraries provide functionality by accessing the underlying operating or hardware platforms. For example, the use of floating point arithmetic or array/vector processing that use array processors or multiple cores. These considerations can often blur the boundary between standard application runtime libraries and language specific runtime libraries. Often compilers provide copies of runtime libraries optimized for the features of the OS and the hardware. | Runtime libraries provide functionality by accessing the underlying operating or hardware platforms. For example, the use of floating point arithmetic or array/vector processing that use array processors or multiple cores. These considerations can often blur the boundary between standard application runtime libraries and language specific runtime libraries. Often compilers provide copies of runtime libraries optimized for the features of the OS and the hardware. | ||
| - | The concept of a runtime library should not be confused with an ordinary program library like those created by application programmers or delivered as third party such as [[dido:public:ra:xapend:xapend.a_glossary:d:dll]] or [[dido:public:ra:xapend:xapend.a_glossary:s:so]], meaning a program library linked at run time. For example, the programming language C requires only a minimal runtime library (commonly called ''crt0'') but defines a large standard library (called ''C standard library'') that each implementation delivers. | + | The concept of a runtime library should not be confused with an ordinary program library like those created by application programmers or delivered as third party such as [[dido:public:ra:xapend:xapend.a_glossary:d:dll]] or [[dido:public:ra:xapend:xapend.a_glossary:s:so]], meaning a program library linked at run time. For example, the [[dido:public:ra:xapend:xapend.a_glossary:p:programlang|programming language]] C requires only a minimal runtime library (commonly called ''crt0'') but defines a large standard library (called ''C standard library'') that each implementation delivers. |
| - | Consequently, the successful execution of an application depends on the proper versions and revisions of all other the Relocatable Objects. It also means that some kinds of errors can only be caught at execution or run time. These kinds of errors are best caught using strategic testing methodologies and strategies such as [[dido:public:ra:xapend:xapend.a_glossary:r:regressiontesting | regression]] or [[dido:public:ra:xapend:xapend.a_glossary:u:unittesting| unit]] testing (see: [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:testability | testability]] for more on testing). | + | Consequently, the successful execution of an application depends on the proper versions and revisions of all other the Relocatable Objects. It also means that some kinds of errors can only be caught at execution or run time. These kinds of errors are best caught using strategic testing methodologies and strategies such as [[dido:public:ra:xapend:xapend.a_glossary:r:regressiontesting | regression]] or [[dido:public:ra:xapend:xapend.a_glossary:u:unittesting| unit testing]](see: [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:testability | testability]] for more on testing). |
dido/public/ra/1.4_req/1_func/platform/sw_arch.1628870187.txt.gz · Last modified: 2021/08/13 11:56 by murphy
