|
Check-in Number:
|
1699 | |
| Date: |
2002-Jan-30 12:55:52 (local)
2002-Jan-30 11:55:52 (UTC) |
| User: | rse |
| Branch: | |
| Comment: |
forget to mention 'cleanup' in namespace mapping |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/ex/ex.pod 1.11 -> 1.12
--- ex.pod 2002/01/30 11:11:09 1.11
+++ ex.pod 2002/01/30 11:55:52 1.12
@@ -300,18 +300,19 @@
B<OSSP ex> implementation consistently uses the B<ex_>, B<__ex_>
and B<__EX_> prefixes for namespace protection. But at least the
-B<ex_> prefix for the API macros B<ex_try>, B<ex_catch>, B<ex_throw>,
-B<ex_rethrow> and B<ex_shield> sometimes have a unpleasant optical
-appearance. Especially because B<OSSP rc> is modeled after the exception
-facility in B<ISO-C++> where there is no such prefix on the directives.
+B<ex_> prefix for the API macros B<ex_try>, B<ex_cleanup>, B<ex_catch>,
+B<ex_throw>, B<ex_rethrow> and B<ex_shield> sometimes have a unpleasant
+optical appearance. Especially because B<OSSP rc> is modeled after the
+exception facility in B<ISO-C++> where there is no such prefix on the
+directives.
For this B<OSSP ex> optionally provides the ability to provide
additional namespace mappings for those API macros. By default (define
C<__EX_NS_USE_CXX__> or as long as C<__EX_NS_USE_CUSTOM__> and
C<__cplusplus> is not defined) you can additional C++ style macros
-named B<catch>, B<throw>, B<rethrow> and B<shield>. As an alternative
-you can define C<__EX_NS_USE_UCCXX__> to get the same but with an (more
-namespace safe) upper case first letter.
+named B<catch>, B<cleanup>, B<throw>, B<rethrow> and B<shield>. As an
+alternative you can define C<__EX_NS_USE_UCCXX__> to get the same but
+with an (more namespace safe) upper case first letter.
=head1 MULTITHREADING ENVIRONMENTS
|
|
