|
|
Boost-Commit : |
From: chochlik_at_[hidden]
Date: 2008-04-22 03:36:59
Author: matus.chochlik
Date: 2008-04-22 03:36:59 EDT (Tue, 22 Apr 2008)
New Revision: 44713
URL: http://svn.boost.org/trac/boost/changeset/44713
Log:
Made minor changes to documentation
Text files modified:
sandbox/mirror/libs/doc/xml/mirror/_library.xml | 12 ++++++++++--
sandbox/mirror/libs/doc/xml/mirror/sections/char_type.xml | 2 +-
sandbox/mirror/libs/doc/xml/mirror/sections/overview.xml | 4 ++--
3 files changed, 13 insertions(+), 5 deletions(-)
Modified: sandbox/mirror/libs/doc/xml/mirror/_library.xml
==============================================================================
--- sandbox/mirror/libs/doc/xml/mirror/_library.xml (original)
+++ sandbox/mirror/libs/doc/xml/mirror/_library.xml 2008-04-22 03:36:59 EDT (Tue, 22 Apr 2008)
@@ -32,12 +32,20 @@
</revision>
<revision id="20080417_1855CET" major="0" minor="1" micro="3" author="m_ch">
- Added an elaborate example on class registration and usage
- - Done major modifications to multiple sources
+ - Made major modifications to multiple sources
</revision>
<revision id="20080418" major="0" minor="1" micro="4" author="m_ch">
- Added two examples (incomplete)
- - Done some modifications to multiple sources
+ - Made some modifications to multiple sources
- Minor updates to documentation
</revision>
+ <revision id="20080421" major="0" minor="1" micro="5" author="m_ch">
+ - Added support for access to the inherited member attributes of a class
+ - Updated the example on virtual inheritance
+ - Updated the example on serialization (still unfinished)
+ </revision>
+ <revision id="20080422" major="0" minor="1" micro="6" author="m_ch">
+ - Made minor updates to documentation
+ </revision>
</revisions>
</library>
Modified: sandbox/mirror/libs/doc/xml/mirror/sections/char_type.xml
==============================================================================
--- sandbox/mirror/libs/doc/xml/mirror/sections/char_type.xml (original)
+++ sandbox/mirror/libs/doc/xml/mirror/sections/char_type.xml 2008-04-22 03:36:59 EDT (Tue, 22 Apr 2008)
@@ -11,7 +11,7 @@
The <cpp_expr>BOOST_USE_WIDE_CHARS</cpp_expr> symbol is in the current implementetion automatically defined, if the <cpp_expr>UNICODE</cpp_expr> symbol is defined (this PP symbol switches between narrow/wide chars on Win32).
</note>
<paragraph>
- 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.
+ 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.
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.
</paragraph>
<note>
Modified: sandbox/mirror/libs/doc/xml/mirror/sections/overview.xml
==============================================================================
--- sandbox/mirror/libs/doc/xml/mirror/sections/overview.xml (original)
+++ sandbox/mirror/libs/doc/xml/mirror/sections/overview.xml 2008-04-22 03:36:59 EDT (Tue, 22 Apr 2008)
@@ -4,7 +4,7 @@
The <lib_name_ref/> library is a compile-time reflection library, intended to be proposed as a <boost/> library at some point in the future.
</paragraph>
<paragraph>
- 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.
+ 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.
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.
</paragraph>
<paragraph>
@@ -20,7 +20,7 @@
Similar to the above and basically to serialization, a custom debugger or a logging facility can use reflection to log, show and possibly modify the values of examined instances.
</item>
<item title="implementation of several design patterns">
- 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).
+ Having a suitable reflection facility, we can easily implement several design patterns like factories, decorators, proxies or mementos.
</item>
</items>
</paragraph>
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk