Changeset 44713


Ignore:
Timestamp:
Apr 22, 2008, 7:36:59 AM (10 years ago)
Author:
matus.chochlik
Message:

Made minor changes to documentation

Location:
sandbox/mirror/libs/doc/xml/mirror
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • sandbox/mirror/libs/doc/xml/mirror/_library.xml

    r44552 r44713  
    3333                <revision id="20080417_1855CET" major="0" minor="1" micro="3" author="m_ch">
    3434                        - Added an elaborate example on class registration and usage
    35                         - Done major modifications to multiple sources
     35                        - Made major modifications to multiple sources
    3636                </revision>
    3737                <revision id="20080418" major="0" minor="1" micro="4" author="m_ch">
    3838                        - Added two examples (incomplete)
    39                         - Done some modifications to multiple sources
     39                        - Made some modifications to multiple sources
    4040                        - Minor updates to documentation
     41                </revision>
     42                <revision id="20080421" major="0" minor="1" micro="5" author="m_ch">
     43                        - Added support for access to the inherited member attributes of a class
     44                        - Updated the example on virtual inheritance
     45                        - Updated the example on serialization (still unfinished)
     46                </revision>
     47                <revision id="20080422" major="0" minor="1" micro="6" author="m_ch">
     48                        - Made minor updates to documentation
    4149                </revision>
    4250        </revisions>
  • sandbox/mirror/libs/doc/xml/mirror/sections/char_type.xml

    r44494 r44713  
    1212        </note>
    1313        <paragraph>
    14                 This approach allows to switch the character type without the need to do any changes to the code. A feature that is handy in some situations. Since the definition of <cpp_expr>bchar</cpp_expr> is always the same as the definition of <cpp_expr>TCHAR</cpp_expr> on Windows, this also allows smooth cooperation between <boost/> and WinAPI with both <cpp_expr>char</cpp_expr>s and <cpp_expr>wchar_t</cpp_expr>s.
     14                This approach allows to switch the character type without the need to do any changes to the code. A feature that is handy in some situations. Since the definition of <cpp_expr>bchar</cpp_expr> is always the same as the definition of <cpp_expr>TCHAR</cpp_expr> on Windows, this also allows smooth cooperation between <lib_name_ref/> and WinAPI with both <cpp_expr>char</cpp_expr>s and <cpp_expr>wchar_t</cpp_expr>s.
    1515                Any WinAPI function that takes <cpp_expr>TCHAR</cpp_expr> or a pointer to <cpp_expr>TCHAR</cpp_expr> can be safely used with <cpp_expr>bchar</cpp_expr>. Thus it is better, safer and more robust to call <cpp_expr>LoadLibrary</cpp_expr> with a <cpp_expr>bchar*</cpp_expr> argument than to directly call <cpp_expr>LoadLibraryA</cpp_expr> with <cpp_expr>char*</cpp_expr> argument or <cpp_expr>LoadLibraryW</cpp_expr> with <cpp_expr>wchar_t*</cpp_expr> argument.
    1616        </paragraph>
  • sandbox/mirror/libs/doc/xml/mirror/sections/overview.xml

    r44471 r44713  
    55        </paragraph>
    66        <paragraph>
    7                 Reflection is a valuable tool when programming applications where instances of different types and classes need to be treated in a uniform manner. This includes, but is not limited to persistence-related operations like serialization or operations like marshalling.
     7                Reflection is a valuable tool when programming applications where instances of different types and classes need to be treated in a uniform manner. This includes, but is not limited to persistence-related operations like serialization, object-relational mapping or operations like marshalling.
    88                Reflection allows to separate the definition of types from the algorithms that are working on the instances of theese types and vice versa. Thus an existing algorithm can be applied to any type recognized by the reflection facility. Well, at least in theory. There are as always exceptions.
    99        </paragraph>
     
    2121                        </item>
    2222                        <item title="implementation of several design patterns">
    23                                 Having a suitable reflection facility, we can easily implement several design patterns like factories, decorators, proxies or mementos (not to be confused with the known freshmaker).
     23                                Having a suitable reflection facility, we can easily implement several design patterns like factories, decorators, proxies or mementos.
    2424                        </item>
    2525                </items>
Note: See TracChangeset for help on using the changeset viewer.