|
Check-in Number:
|
1965 | |
| Date: |
2002-Mar-07 13:19:46 (local)
2002-Mar-07 12:19:46 (UTC) |
| User: | rse |
| Branch: | |
| Comment: |
Yeah, reduce the TODO list to zero items\! |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/var/TODO 1.28 -> 1.29
--- TODO 2002/03/07 12:11:09 1.28
+++ TODO 2002/03/07 12:19:46 1.29
@@ -1,4 +1,4 @@
- OSSP var
- o document exception handling
+ OSSP var
+ ========
|
|
ossp-pkg/var/var.pod 1.29 -> 1.30
--- var.pod 2002/03/07 12:11:09 1.29
+++ var.pod 2002/03/07 12:19:46 1.30
@@ -686,6 +686,22 @@
might have introduced now quoted pairs into the output text, which you
need to expand to get the desired effect.
+=head1 EXCEPTION HANDLING
+
+B<OSSP var> can be optionally built with support for exception handling
+via B<OSSP ex> (see http://www.ossp.org/pkg/lib/ex/). For this it has to
+be configured with the GNU Autoconf option C<--with-ex>. The difference
+then is that the B<OSSP var> API functions throw exceptions instead of
+returning C<VAR_ERR_XXX> return codes.
+
+The thrown exceptions can be identified as B<OSSP var> exceptions by
+checking the exception attribute C<ex_class>. It is the B<OSSP var>
+API symbol C<var_id> for all B<OSSP var> exceptions. The C<ex_object>
+attribute is always C<NULL>. The C<ex_value> attribute is the
+C<var_rc_t> which forced the throwing of the exception.
+
+Exception throwing can be suppressed with C<ex_shield> only.
+
=head1 EXAMPLE (DEVELOPER)
The following simple but complete program illustrates the full usage
|
|
