Menu
▾
▴
[Corelinux-clcvs] CVS: htdocs/develop corelinux.css,1.4,1.5 develop.dvi,1.9,1.10 develop.pdf,1.9,1.10 develop.ps,1.9,1.10 develop.tex,1.9,1.10 develop.txt,1.6,1.7
|
From: Frank V. C. <fr...@us...> - 2000-10-07 17:17:01
|
Update of /cvsroot/corelinux/htdocs/develop In directory slayer.i.sourceforge.net:/tmp/cvs-serv17012 Modified Files: corelinux.css develop.dvi develop.pdf develop.ps develop.tex develop.txt Log Message: Documentation updates Index: corelinux.css =================================================================== RCS file: /cvsroot/corelinux/htdocs/develop/corelinux.css,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -r1.4 -r1.5 *** corelinux.css 2000/09/05 01:37:53 1.4 --- corelinux.css 2000/10/07 17:16:56 1.5 *************** *** 1,3 **** ! BODY { background-color: #FFFFFF } A { text-decoration: none; color #6666FF; } --- 1,3 ---- ! BODY { background-color: #FFFFFF; } A { text-decoration: none; color #6666FF; } *************** *** 14,18 **** SPAN.boxspace { font-size: 2pt; } ! A.maintitlebar { color: #FFFFFF; } A.bottombar { color: #FFFFFF; text-decoration: underline; } A.sortbutton { color: #FFFFFF; text-decoration: underline; } --- 14,18 ---- SPAN.boxspace { font-size: 2pt; } ! A.maintitlebar { color: #ffffff; } A.bottombar { color: #FFFFFF; text-decoration: underline; } A.sortbutton { color: #FFFFFF; text-decoration: underline; } *************** *** 21,28 **** A.date { color: #ff0000; text-decoration: underline; } SPAN.alignright { text-align: right } ! SPAN.maintitlebar { font-size: 10pt; color: #FFFFFF; font-weight: bold } SPAN.bottombar { font-size: 10pt; color: #FFFFFF; font-weight: bold } ! SPAN.titlebar { text-align: center; font-size: 10pt; color: #FFFFFF; font-weight: bold } TD.featurebox { font-size: small; } TD.newsbox { font-size: 8pt; } ! TD.menus { color: #BBBBBB; } --- 21,29 ---- A.date { color: #ff0000; text-decoration: underline; } SPAN.alignright { text-align: right } ! SPAN.maintitlebar { color: #ffffff; font-weight: bold } SPAN.bottombar { font-size: 10pt; color: #FFFFFF; font-weight: bold } ! SPAN.titlebar { text-align: center; color: #FFFFFF; font-weight: bold } ! SPAN.tablebar { color: #FFFFFF; font-weight: bold } TD.featurebox { font-size: small; } TD.newsbox { font-size: 8pt; } ! TD.menus { color: #d5d7d9; } Index: develop.dvi =================================================================== RCS file: /cvsroot/corelinux/htdocs/develop/develop.dvi,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -r1.9 -r1.10 Binary files /tmp/cvsKZYXSQ and /tmp/cvsyO9Ihx differ Index: develop.pdf =================================================================== RCS file: /cvsroot/corelinux/htdocs/develop/develop.pdf,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -r1.9 -r1.10 Binary files /tmp/cvsoBWX0V and /tmp/cvs4o3VsW differ Index: develop.ps =================================================================== RCS file: /cvsroot/corelinux/htdocs/develop/develop.ps,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -r1.9 -r1.10 *** develop.ps 2000/09/05 01:37:53 1.9 --- develop.ps 2000/10/07 17:16:56 1.10 *************** *** 9,13 **** %DVIPSCommandLine: dvips -o develop.ps develop.dvi %DVIPSParameters: dpi=600, compressed ! %DVIPSSource: TeX output 2000.09.04:2134 %%BeginProcSet: texc.pro %! --- 9,13 ---- %DVIPSCommandLine: dvips -o develop.ps develop.dvi %DVIPSParameters: dpi=600, compressed ! %DVIPSSource: TeX output 2000.10.07:1301 %%BeginProcSet: texc.pro %! *************** *** 78,114 **** %%EndSetup %%Page: 1 1 ! 1 0 bop 1948 4421 5 2647 v eop %%Page: 2 2 ! 2 1 bop 0 -191 2989 4 v 2303 2249 29 4 v 2432 2249 V eop %%Page: 3 3 3 2 bop 0 -191 2989 4 v eop %%Page: 4 4 ! 4 3 bop 0 -191 2989 4 v 569 5263 29 4 v eop %%Page: 5 5 ! 5 4 bop 0 -191 2989 4 v -28 419 3957 4 v -28 2534 4 2115 ! v 3925 2534 V -28 2537 3957 4 v 2098 2617 29 4 v -28 ! 3517 3957 4 v -28 4842 4 1325 v 3925 4842 V -28 4845 ! 3957 4 v 2074 4925 29 4 v eop %%Page: 6 6 ! 6 5 bop 0 -191 2989 4 v 569 91 29 4 v 665 779 V -28 877 ! 3957 4 v -28 1963 4 1087 v 3925 1963 V -28 1966 3957 ! 4 v 2146 2046 29 4 v 665 2322 V -28 2420 3957 4 v -28 ! 3506 4 1087 v 3925 3506 V -28 3509 3957 4 v 2099 3589 ! 29 4 v 665 3866 V -28 3964 3957 4 v -28 5163 4 1199 v ! 3925 5163 V -28 5166 3957 4 v 2122 5246 29 4 v eop %%Page: 7 7 ! 7 6 bop 0 -191 2989 4 v 665 91 29 4 v -28 214 3957 4 ! v -28 1413 4 1199 v 3925 1413 V -28 1416 3957 4 v 2122 ! 1497 29 4 v 665 1776 V -28 1879 3957 4 v -28 3078 4 1199 ! v 3925 3078 V -28 3081 3957 4 v 2170 3161 29 4 v 665 ! 3448 V 665 3636 V 665 3824 V 2078 4011 V eop ! %%Page: 8 8 ! 8 7 bop 0 -191 2989 4 v -28 40 3957 4 v -28 1239 4 1199 ! v 3925 1239 V -28 1242 3957 4 v 2051 1322 29 4 v -28 ! 1466 3957 4 v -28 3230 4 1764 v 3925 3230 V -28 3233 ! 3957 4 v 2170 3313 29 4 v -28 3456 3957 4 v -28 5220 ! 4 1764 v 3925 5220 V -28 5223 3957 4 v 2077 5303 29 4 v eop %%Page: 9 9 9 8 bop 0 -191 2989 4 v -28 3 3957 4 v -28 1365 4 1362 --- 78,115 ---- %%EndSetup %%Page: 1 1 ! 1 0 bop 1948 4610 5 2764 v eop %%Page: 2 2 ! 2 1 bop 0 -191 2989 4 v 2303 2648 29 4 v 2432 2648 V eop %%Page: 3 3 3 2 bop 0 -191 2989 4 v eop %%Page: 4 4 ! 4 3 bop 0 -191 2989 4 v eop %%Page: 5 5 ! 5 4 bop 0 -191 2989 4 v 569 920 29 4 v -28 1040 3957 ! 4 v -28 3155 4 2115 v 3925 3155 V -28 3158 3957 4 v 2098 ! 3238 29 4 v 569 3508 V -28 3629 3957 4 v -28 4953 4 1325 ! v 3925 4953 V -28 4956 3957 4 v 2074 5036 29 4 v eop %%Page: 6 6 ! 6 5 bop 0 -191 2989 4 v 665 386 29 4 v -28 486 3957 4 ! v -28 1572 4 1087 v 3925 1572 V -28 1575 3957 4 v 2146 ! 1655 29 4 v 665 1938 V -28 2038 3957 4 v -28 3124 4 1087 ! v 3925 3124 V -28 3127 3957 4 v 2099 3207 29 4 v 665 ! 3490 V -28 3590 3957 4 v -28 4789 4 1199 v 3925 4789 ! V -28 4792 3957 4 v 2122 4872 29 4 v 665 5155 V 665 5340 ! V eop %%Page: 7 7 ! 7 6 bop 0 -191 2989 4 v -28 226 3957 4 v -28 1425 4 1199 ! v 3925 1425 V -28 1428 3957 4 v 2122 1508 29 4 v -28 ! 2037 3957 4 v -28 3236 4 1199 v 3925 3236 V -28 3239 ! 3957 4 v 2170 3319 29 4 v -28 3835 3957 4 v -28 5034 ! 4 1199 v 3925 5034 V -28 5037 3957 4 v 2051 5117 29 4 v eop + %%Page: 8 8 + 8 7 bop 0 -191 2989 4 v 665 91 29 4 v 665 265 V -28 374 + 3957 4 v -28 2137 4 1764 v 3925 2137 V -28 2140 3957 + 4 v 2170 2220 29 4 v 665 2459 V -28 2568 3957 4 v -28 + 4331 4 1764 v 3925 4331 V -28 4334 3957 4 v 2077 4414 + 29 4 v 2078 4632 V eop %%Page: 9 9 9 8 bop 0 -191 2989 4 v -28 3 3957 4 v -28 1365 4 1362 Index: develop.tex =================================================================== RCS file: /cvsroot/corelinux/htdocs/develop/develop.tex,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -r1.9 -r1.10 *** develop.tex 2000/09/05 01:37:53 1.9 --- develop.tex 2000/10/07 17:16:57 1.10 *************** *** 471,480 **** \newpage ! \subsection{Frameworks} \label{sec:CoreFramework} A framework is defined as a facilitating backbone which combines sets of related components for a specific purpose or domain. A distinguishing feature of a framework is that it defines a generic design that supports a bi-directional flow of control between the application and itself. ! \subsubsection{Framework Support} \label{sec:FrameworkSupport} --- 471,480 ---- \newpage ! \section{Frameworks} \label{sec:CoreFramework} A framework is defined as a facilitating backbone which combines sets of related components for a specific purpose or domain. A distinguishing feature of a framework is that it defines a generic design that supports a bi-directional flow of control between the application and itself. ! \subsection{Framework Support} \label{sec:FrameworkSupport} *************** *** 483,487 **** The framework library (libclfw) provides a number of support objects and framework abstractions as defined below. ! \subsubsection{Meta-class MetaType} \label{sec:Meta-class-MetaType} --- 483,487 ---- The framework library (libclfw) provides a number of support objects and framework abstractions as defined below. ! \subsection{Meta-class MetaType} \label{sec:Meta-class-MetaType} *************** *** 490,494 **** Therefore a meta-class instance is used to capture (model) the type information about a class, and subsequently, it's instances. For example, we can consider that "aaaaa" is an instance of a ascii string, and that string is of type MetaTypeAsciiString. Within MetaTypeAsciiString we can convey information about constraints (upper and lower bound, each character is 8 bits, must terminate with null, etc.) as well as it's relationship to other types. In the example, MetaTypeAsciiString can be modeled as a child of MetaTypeString. ! \subsubsection{Ontology} \label{sec:Ontology} A ontology is an explicit specification of some topic. It is a formal and declarative representation which includes the vocabulary (or names) for referring to terms in that subject area and the logical statements that describe what the terms are, how they are related to each other, and how they can or cannot be related to each other. Ontologies therefore provide a vocabulary for representing and communicating knowledge about some topic and a set of relationships that hold among the terms in that vocabulary. --- 490,499 ---- Therefore a meta-class instance is used to capture (model) the type information about a class, and subsequently, it's instances. For example, we can consider that "aaaaa" is an instance of a ascii string, and that string is of type MetaTypeAsciiString. Within MetaTypeAsciiString we can convey information about constraints (upper and lower bound, each character is 8 bits, must terminate with null, etc.) as well as it's relationship to other types. In the example, MetaTypeAsciiString can be modeled as a child of MetaTypeString. ! \subsection{MetaType Macros} ! \label{sec:Meta-Type-Macros} ! ! The following macros, and their use, are detailed below: ! ! \subsection{Ontology} \label{sec:Ontology} A ontology is an explicit specification of some topic. It is a formal and declarative representation which includes the vocabulary (or names) for referring to terms in that subject area and the logical statements that describe what the terms are, how they are related to each other, and how they can or cannot be related to each other. Ontologies therefore provide a vocabulary for representing and communicating knowledge about some topic and a set of relationships that hold among the terms in that vocabulary. *************** *** 496,499 **** --- 501,509 ---- The CoreLinux++ support for ontologies are in the form of MetaType object declarations and definitions joined through associations into a hierarchy, or tree. It is through access to this tree that components or applications can reason with the class types involved in the ontology. + \subsection{MetaType Ontology} + \label{sec:MetaTypeOntology} + + The base framework library (libclfw++) contains a number of types that, via the MetaType macros, forms a ``starter kit'' type ontology. The types defined include: + \subsection{Common franework abstractions} \label{sec:CommonFrameworkAbstractions} *************** *** 505,508 **** --- 515,523 ---- Whether managing graphic libraries, supporting plug-ins for extension, or dynamically calling shared library functions, applications often have a need to load information at run-time through the support of some library or operating system facility. The Library Load Framework supplies the extensible object types and behvioral semantics for such activities. + + \subsection{Persistence} + \label{sec:Persist} + + There are many C++ applications that require the object instances to be saved and loaded for use across application or machine sessions. \bibliographystyle{plainnat} Index: develop.txt =================================================================== RCS file: /cvsroot/corelinux/htdocs/develop/develop.txt,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -r1.6 -r1.7 *** develop.txt 2000/09/05 01:37:53 1.6 --- develop.txt 2000/10/07 17:16:57 1.7 *************** *** 9,13 **** ! Revision: 1.8 Created on June 04, 2000 --- 9,13 ---- ! Revision: 1.9 Created on June 04, 2000 *************** *** 16,69 **** This document describes how to build applications|with CoreLinux++ Standards. This is ! the CoreLinux++ Development Guide. || ! ! | ! Contents || 2.4.9 CoreLinux++ Documen- ! | tation for Standards, ! | ! 1 Introduction 2 || Class Reference, Require- ! | ments, Analysis, and Design 4 | - | - 2 Setting Up for CoreLinux++ builds 2 ||3 Standard Development Process 4 - - 2.1 Getting Things Rolling . . . . . . 2 || - 4 Developing with CoreLinux++ 4 - 2.2 Make Environment . . . . . . . . 2 || 4.1 Using autoconf . . . . . . . . . . 4 - - 2.3 Setting up for CoreLinux++ Ex- || 4.2 Macros . . . . . . . . . . . . . . . 4 - ecution . . . . . . . . . . . . . . . 2 | | ! 2.4 Directory Structure . . . . . . . . 2 | 5 Class Library Internals 7 | ! 2.4.1 The Root Directory . . . 3 | 5.1 Foundation Classes . . . . . . . . 7 | - 2.4.2 The Root Include . . . . . 3 || 5.2 Inter-Process Communication . . 9 - - 2.4.3 The Root Source Root . . 3 || 5.2.1 Semaphore and Semaphore- - - 2.4.4 Class Library Source Root 3 || Group . . . . . . . . . . . 9 - 5.2.2 Threads . . . . . . . . . . 9 - 2.4.5 CoreLinux Class Library || 5.3 Design Patterns . . . . . . . . . . 9 - Source . . . . . . . . . . . 3 | - | 5.4 Frameworks . . . . . . . . . . . . 10 - 2.4.6 Additional Class Library | 5.4.1 Framework Support . . . 10 - Source . . . . . . . . . . . 4 || 5.4.2 Meta-class MetaType . . 10 - - 2.4.7 The Test Driver and Ex- || 5.4.3 Ontology . . . . . . . . . 10 - ample Code Root . . . . . 4 || 5.5 Common franework abstractions 10 - - 2.4.8 Example application source 4 || 5.5.1 Library Load . . . . . . . 10 - ! Copyright notice CoreLinux++ Copyright cO 1999, 2000 CoreLinux Consortium ! Revision 1.8 Last Modified: September 5, 2000 This material may be distributed only subject to the terms and conditions set forth in the Open - Publication License. 1 ^L --- 16,57 ---- This document describes how to build applications|with CoreLinux++ Standards. This is ! the CoreLinux++ Development Guide. | | | ! Contents ||3 Standard Development Process 4 | ! 1 Introduction 2 ||4 Developing with CoreLinux++ 4 | ! 2 Setting Up for CoreLinux++ builds 2 || 4.1 Using autoconf . . . . . . . . . . 4 ! 2.1 Getting Things Rolling . . . . . . 2 || 4.2 Macros . . . . . . . . . . . . . . . 5 ! 2.2 Make Environment . . . . . . . . 2 || ! 2.3 Setting up for CoreLinux++ Ex- ||5 Class Library Internals 8 ! ecution . . . . . . . . . . . . . . . 2 | 5.1 Foundation Classes . . . . . . . . 9 ! 2.4 Directory Structure . . . . . . . . 3 || 5.2 Inter-Process Communication . . 9 ! 2.4.1 The Root Directory . . . 3 || 5.2.1 Semaphore and Semaphore- ! 2.4.2 The Root Include . . . . . 3 || Group . . . . . . . . . . . 9 ! 2.4.3 The Root Source Root . . 3 || 5.2.2 Threads . . . . . . . . . . 9 ! 2.4.4 Class Library Source Root 4 | 5.3 Design Patterns . . . . . . . . . . 9 ! 2.4.5 CoreLinux Class Library || ! Source . . . . . . . . . . . 4 ||6 Frameworks 10 ! 2.4.6 Additional Class Library || 6.1 Framework Support . . . . . . . 10 ! Source . . . . . . . . . . . 4 || 6.2 Meta-class MetaType . . . . . . 10 ! 2.4.7 The Test Driver and Ex- || ! ample Code Root . . . . . 4 | 6.3 MetaType Macros . . . . . . . . 10 ! 2.4.8 Example application source 4 || 6.4 Ontology . . . . . . . . . . . . . 10 ! 2.4.9 CoreLinux++ Documen- || 6.5 MetaType Ontology . . . . . . . 10 ! tation for Standards, || 6.6 Common franework abstractions 11 ! Class Reference, Require- || 6.6.1 Library Load . . . . . . . 11 ! ments, Analysis, and Design 4 | 6.7 Persistence . . . . . . . . . . . . 11 Copyright notice CoreLinux++ Copyright cO 1999, 2000 CoreLinux Consortium ! Revision 1.9 Last Modified: September 5, 2000 This material may be distributed only subject to the terms and conditions set forth in the Open + + 1 ^L *************** *** 73,76 **** --- 61,67 ---- + Publication License. + + 1 Introduction *************** *** 133,138 **** --- 124,134 ---- install-path/lib when you 'make install'. + 2 + ^L + 2___SETTING_UP_FOR_CORELINUX++_BUILDS________________________2.4___Directory_Structure______ + + 2.4 Directory Structure *************** *** 144,155 **** - - 2 - ^L - 2___SETTING_UP_FOR_CORELINUX++_BUILDS________________________2.4___Directory_Structure______ - - - - \corelinux ; The root corelinux directory \corelinux ; Root include directory (libcorelinux++ includes) --- 140,143 ---- *************** *** 207,210 **** --- 195,202 ---- All source code for CoreLinux++ projects are located from this point in the development tree. + 3 + ^L + 4___DEVELOPING_WITH_CORELINUX++_____________________________________________________________ + *************** *** 222,232 **** Source code specific to libcorelinux++, the result of which is a Class Libraries, is located here. - 3 - ^L - 4___DEVELOPING_WITH_CORELINUX++_____________________________________________________________ - 2.4.6 Additional Class Library Source --- 214,220 ---- *************** *** 283,286 **** --- 271,281 ---- ],[ echo "You need to install corelinux. see http://corelinux.sourceforge.net" + 4 + ^L + 4___DEVELOPING_WITH_CORELINUX++_____________________________________________4.2___Macros____ + + + + exit; ],) *************** *** 294,313 **** types and classes. Don't be shy at using them and what they provide. - - o DECLARE_TYPE declares a new type as in code 4.1 on the following page - 4 - ^L - 4___DEVELOPING_WITH_CORELINUX++_____________________________________________4.2___Macros____ - - - - - - || * - * | - || * - * | _______________________________________________________________________________________________________________________* *___|||| --- 289,296 ---- types and classes. Don't be shy at using them and what they provide. + ||| o DECLARE_TYPE declares a new type as in code 4.1 * + * || _______________________________________________________________________________________________________________________* *___|||| *************** *** 381,384 **** --- 364,370 ---- + + o DECLARE_CLASS declares a new class as in code 4.2 this macro is expecially used for forward + _______________________________________________________________________________________________________________________* *___|||| *************** *** 428,431 **** --- 414,419 ---- + class declaration or to ensure the declaration of the associated pointer and reference types. + 5 ^L *************** *** 435,443 **** - o DECLARE_CLASS declares a new class as in code 4.2 on the page before this macro is expecially - used for forward class declaration or to ensure the declaration of the associated pointer and - reference types. - - Corelinux++ uses STL containers and algorithm. In order to provide the same services DECLARE_TYPE and DECLARE_CLASS, several macros are provided : --- 423,426 ---- *************** *** 570,582 **** Code 4.5: CORELINUX_STACK macro 6 ^L ! 5___CLASS_LIBRARY_INTERNALS_________________________________________________________________ - o CORELINUX_QUEUE defines a STL std::dequeue as in code 4.6 _______________________________________________________________________________________________________________________* *___|||| --- 553,574 ---- Code 4.5: CORELINUX_STACK macro + + + o CORELINUX_QUEUE defines a STL std::dequeue as in code 4.6 on the next page + + + o CORELINUX_SET defines a STL std::set as in code 4.7 on the following page + + + 6 ^L ! 4___DEVELOPING_WITH_CORELINUX++_____________________________________________4.2___Macros____ + _______________________________________________________________________________________________________________________* *___|||| *************** *** 620,630 **** *___ | Code 4.6: CORELINUX_QUEUE macro - - - - || o CORELINUX_SET defines a STL std::set as in code 4.7 * - * | _______________________________________________________________________________________________________________________* ! *___|| || #include <CORELINUX/Set.hpp> * * | --- 612,617 ---- *___ | Code 4.6: CORELINUX_QUEUE macro _______________________________________________________________________________________________________________________* ! *___|||| || #include <CORELINUX/Set.hpp> * * | *************** *** 666,700 **** *___ | Code 4.7: CORELINUX_SET macro - o CORELINUX_MULTISET defines a STL std::multiset as in code 4.8 on the next page - - - o CORELINUX_MAP defines a STL std::map as in code 4.9 on the following page - - - o CORELINUX_MULTIMAP defines a STL std::multimap as in code 4.10 on the next page - - - Note that for all these macro, except CORELINUX_STACK, the Iterator type is defined also, see - for example the code 4.11 on page 9 - 5 Class Library Internals - - - The Class Library Internals is your guide into the inner workings of libcorelinux++. This is a - useful section for those interested in how it works, or how they can contribute to make it better. - - - - 5.1 Foundation Classes - - - This section covers the foundational classes of the class library. - - - 7 - ^L - 5___CLASS_LIBRARY_INTERNALS___________________________________5.1___Foundation_Classes______ - - - _______________________________________________________________________________________________________________________* *___|||| --- 653,656 ---- *************** *** 739,744 **** Code 4.8: CORELINUX_MULTISET macro _______________________________________________________________________________________________________________________* ! *___|||| || #include <CORELINUX/Map.hpp> * * | --- 695,714 ---- Code 4.8: CORELINUX_MULTISET macro + + + 7 + ^L + 5___CLASS_LIBRARY_INTERNALS_________________________________________________________________ + + + + + o CORELINUX_MULTISET defines a STL std::multiset as in code 4.8 on the page before + + + || o CORELINUX_MAP defines a STL std::map as in code 4.9 * + * | _______________________________________________________________________________________________________________________* ! *___|| || #include <CORELINUX/Map.hpp> * * | *************** *** 799,804 **** Code 4.9: CORELINUX_MAP macro _______________________________________________________________________________________________________________________* ! *___|||| || #include <CORELINUX/Map.hpp> * * | --- 769,778 ---- Code 4.9: CORELINUX_MAP macro + + + || o CORELINUX_MULTIMAP defines a STL std::multimap as in code 4.10 * + * | _______________________________________________________________________________________________________________________* ! *___|| || #include <CORELINUX/Map.hpp> * * | *************** *** 858,864 **** *___ | Code 4.10: CORELINUX_MULTIMAP macro 8 ^L ! 5___CLASS_LIBRARY_INTERNALS______________________5.2___Inter-Process_Communication__________ --- 832,853 ---- *___ | Code 4.10: CORELINUX_MULTIMAP macro + + + Note that for all these macro, except CORELINUX_STACK, the Iterator type is defined also, see + for example the code 4.11 on the following page + + + + 5 Class Library Internals + + + The Class Library Internals is your guide into the inner workings of libcorelinux++. This is a + useful section for those interested in how it works, or how they can contribute to make it better. + + + 8 ^L ! 5___CLASS_LIBRARY_INTERNALS___________________________________5.1___Foundation_Classes______ *************** *** 912,915 **** --- 901,911 ---- + 5.1 Foundation Classes + + + This section covers the foundational classes of the class library. + + + 5.2 Inter-Process Communication *************** *** 933,947 **** 5.3 Design Patterns - - - 9 ^L ! 5___CLASS_LIBRARY_INTERNALS____________________________________________5.4___Frameworks_____ ! 5.4 Frameworks --- 929,940 ---- 5.3 Design Patterns 9 ^L ! 6___FRAMEWORKS______________________________________________________________________________ ! 6 Frameworks *************** *** 952,956 **** ! 5.4.1 Framework Support --- 945,949 ---- ! 6.1 Framework Support *************** *** 964,968 **** ! 5.4.2 Meta-class MetaType --- 957,961 ---- ! 6.2 Meta-class MetaType *************** *** 979,986 **** - 5.4.3 Ontology A ontology is an explicit specification of some topic. It is a formal and declarative representation which includes the vocabulary (or names) for referring to terms in that subject area and the logical --- 972,986 ---- + + 6.3 MetaType Macros + + + The following macros, and their use, are detailed below: + + 6.4 Ontology + A ontology is an explicit specification of some topic. It is a formal and declarative representation which includes the vocabulary (or names) for referring to terms in that subject area and the logical *************** *** 994,1006 **** ! 5.5 Common franework abstractions The following are the abstract frameworks that come with the libclfw library. ! 5.5.1 Library Load --- 994,1019 ---- + + 6.5 MetaType Ontology + ! The base framework library (libclfw++) contains a number of types that, via the MetaType macros, ! forms a "starter kit" type ontology. The types defined include: + 10 + ^L + REFERENCES____________________________________6.6___Common_franework_abstractions___________ + + + + 6.6 Common franework abstractions + + The following are the abstract frameworks that come with the libclfw library. ! 6.6.1 Library Load *************** *** 1012,1022 **** ! 10 ! ^L ! REFERENCES______________________________________________________________REFERENCES__________ ! ! References --- 1025,1033 ---- ! 6.7 Persistence ! There are many C++ applications that require the object instances to be saved and loaded for use ! across application or machine sessions. References *************** *** 1029,1032 **** --- 1040,1044 ---- FSF. GNU Libtool Manual. FSF, 1.3.4 edition, 2000b. + 11 |
