diff options
| author | nanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1999-04-22 21:37:53 +0000 |
|---|---|---|
| committer | nanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 1999-04-22 21:37:53 +0000 |
| commit | 624433d32e8aee171ec058f0ff291889fc46f6c4 (patch) | |
| tree | b4f9112147d10765d8f07406cf2c169e38d3a5f2 /docs | |
| parent | 4934a0c43b3f5b02babd60645d76e19eb11e80fb (diff) | |
| download | ATCD-624433d32e8aee171ec058f0ff291889fc46f6c4.tar.gz | |
Explicitly say TAO try macros is obsolete.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/exceptions.html | 47 |
1 files changed, 26 insertions, 21 deletions
diff --git a/docs/exceptions.html b/docs/exceptions.html index 82d4f6e0978..0994d75aff4 100644 --- a/docs/exceptions.html +++ b/docs/exceptions.html @@ -4,24 +4,29 @@ <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>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>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>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>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>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> @@ -61,7 +66,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> @@ -77,14 +82,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> @@ -168,7 +173,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> @@ -335,7 +340,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); |