diff options
Diffstat (limited to 'docs/exceptions.html')
| -rw-r--r-- | docs/exceptions.html | 47 |
1 files changed, 21 insertions, 26 deletions
diff --git a/docs/exceptions.html b/docs/exceptions.html index 0994d75aff4..82d4f6e0978 100644 --- a/docs/exceptions.html +++ b/docs/exceptions.html @@ -4,29 +4,24 @@ <title>Using ACE try macros for CORBA programming</title> </head> -<body text="#000000" link="#0000ff" vlink="#cc0000" bgcolor="#ffffff"> -<h1>Using ACE try macros for CORBA programming</h1> + <body text="#000000" link="#0000ff" vlink="#cc0000" bgcolor="#ffffff"> + <h1>Using ACE try macros for CORBA programming</h1> -<p>ACE try macros will completely replace TAO try macros soon. If you -are still using TAO try macros in your code, you should replace them -with ACE try macros to avoid possible breakage when we remove TAO try -macros.<\p> + <P>It would be useful if the reader can go through the book, "Advanced + Corba Programming with C++" by Michi & Steve, from pages 307 through + to 322. + </P> -<P>It would be useful if the reader can go through the book, "Advanced -Corba Programming with C++" by Michi & Steve, from pages 307 through -to 322. -</P> - -<P>CORBA::Environment provides a way to handle exceptions when -native c++ exception handling is unavailable or undesirable. -However, writing portable code for both (with and without) native -exception handling capability is very hairy. -</P> + <P>CORBA::Environment provides a way to handle exceptions when + native c++ exception handling is unavailable or undesirable. + However, writing portable code for both (with and without) native + exception handling capability is very hairy. + </P> + <P>ACE provides a set of macros to help dealing with the chaos, + but please keep in mind that no amount of macros is going to + solve the problem perfectly. + </P> -<P>ACE provides a set of macros to help dealing with the chaos, -but please keep in mind that no amount of macros is going to -solve the problem perfectly. -</P> <h3>What's in here?</h3> <ul> @@ -66,7 +61,7 @@ try macros. exceptions from functions it called. By default, ACE try macros assumes that the variable is named <code>ACE_TRY_ENV</code>. <code>ACE_TRY_ENV</code> itself is also a macro which can be - redefined. + redefined. </pre> <P> @@ -82,14 +77,14 @@ try macros. If you are using TAO for writing application programs and you are interested in using exceptions (which is a pretty neat way to go about), the environmnet variable can be brought in to your - scope by the adding a statement <code>ACE_DECLARE_NEW_CORBA_ENV;</code> + scope by the adding a statement <code>ACE_DECLARE_NEW_CORBA_ENV;</code> You can then invoke the methods on the servant from the client side as <pre> object_reference->func_name (x, y, ACE_TRY_ENV); </pre> - - + + Even if you are interested in making calls within the client side, you can define your method like this <pre> @@ -173,7 +168,7 @@ try macros. <li><P>Follow <em>every</em> exception throwing function with <code>ACE_TRY_CHECK</code>. If you are using a TRY block within another try block add a <code>ACE_TRY_CHECK</code> - at the end of this TRY block ie. after + at the end of this TRY block ie. after <code>ACE_ENDTRY</code>. </p> </LI> @@ -340,7 +335,7 @@ macros discussed here. { // Caught an exception, so we need to make some other calls // to continue.. - + ACE_TRY_EX (block1) // basically a label { some_other_call1 (arg1,.. , ACE_TRY_ENV); |