diff options
Diffstat (limited to 'TAO/docs/compiler.html')
| -rw-r--r-- | TAO/docs/compiler.html | 54 |
1 files changed, 20 insertions, 34 deletions
diff --git a/TAO/docs/compiler.html b/TAO/docs/compiler.html index 48444ea81c5..e30da68326f 100644 --- a/TAO/docs/compiler.html +++ b/TAO/docs/compiler.html @@ -17,14 +17,14 @@ TAO IDL Compiler User's Guide</h3> <h3> Scope</h3> This document describes the options and features of TAO IDL compiler. It is not a reference manual or tutorial on OMG IDL. For more information on OMG IDL see the <A -HREF="http://www.omg.org/technology/documents/corba_spec_catalog.htm"> -online CORBA specification</A> and the <A +HREF="http://cgi.omg.org/library/c2indx.html">online CORBA +specification</A> and the <A HREF="http://www.triodia.com/staff/michi-henning.html">Advanced CORBA Programming with C++</A> book. More information on the design of TAO's IDL compiler is also available <A HREF="http://www.cs.wustl.edu/~schmidt/PDF/ami1.pdf">online</A>. Finally, comprehensive documentation on TAO's IDL compiler is -available in the OCI <A HREF="http://www.theaceorb.com/product/index.html">TAO +available in the OCI <A HREF="http://www.theaceorb.com/product/">TAO Developer's Guide</A>.<P> <HR><P> @@ -165,17 +165,6 @@ Note that if you can't use perfect hashing for some reason the next best operation demuxing strategy is binary search, which can be configured using TAO's IDL compiler <A HREF="#options">options</A>.<P> -<HR><P> -<h3>AMI support</h3> - -By default the TAO_IDL compiler generates AMI stubs and skeletons as -described in the CORBA 3.0.3 specification. If you want to use the -old deprecated AMI support, add the following line to your -<code>config.h</code> file and rebuild the core TAO libs and -the TAO_IDL compiler.</p> -<p> -<code>#define TAO_HAS_DEPRECATED_EXCEPTION_HOLDER</code> - <hr><p> <h3><a name="collocation-stubs">Collocation Strategies</a></h3> @@ -283,7 +272,7 @@ also receives other options that are specific to it.<p> <td><tt>anyop_export_macro=</tt><i>macro_name</i></td> <td>The compiler will emit <i>macro_name</i> before each Any operator - or <tt>extern</tt> typecode declaration in the generated stub code, + or <tt>extern</tt> typecode declaration in the generated stub code, this is needed for Windows, which requires special directives to export symbols from DLLs, usually the definition is just a space on unix platforms. This option works only in conjuction with @@ -298,7 +287,7 @@ also receives other options that are specific to it.<p> <td>The compiler will generate code to include <i>include_path</i> at the top of the anyop file header, this is usually a good place to define the export - macro. This option works in conjuction with the -GA option, which generates Any + macro. This option works in conjuction with the -GA option, which generates Any operators and typecodes into a separate set of files.</td> </tr> @@ -323,7 +312,7 @@ also receives other options that are specific to it.<p> <td>This option has the same effect as specifying<br> <tt>-Wb,stub_export_include=</tt><i>include_path</i><br> <tt>-Wb,skel_export_include=</tt><i>include_path</i><br> - <tt>-Wb,anyop_export_include=</tt><i>include_path</i>.<br> + <tt>-Wb,anyop_export_include=</tt><i>include_path</i>.<br> This option goes with the previous option to build DLL containing both stubs and skeletons.</td> </tr> @@ -620,20 +609,17 @@ also receives other options that are specific to it.<p> <tr><a name="Ge flag"> <td><tt>-Ge </tt><i>flag</i></td> - <td>If the value of the flag is 0, operations generated from application IDL will - use native C++ exceptions. If the value of the flag is 1, such operations will - use the <CODE>CORBA::Environment</CODE> variable for passing exceptions. If the - value of the flag is 2, the C++ 'throw' keyword will be used in place of - ACE_THROW_SPEC, ACE_THROW, and ACE_RETHROW (ACE_THROW_RETURN and - TAO_INTERCEPTOR_THROW will still be used). This flag value will also disable - the generation of environment variables in argument lists for all generated - operations, including base class overrides not defined in application IDL.</td> - <td>As of TAO 1.5, support for emulated exceptions is in the process of being - dropped. The environment variable macros are still present in ORB code and in - generated code, but they now expand to nothing and are no longer maintained. - Soon they will be removed altogether, and at that point, no throw, throw spec, - or environment macros will be generated by the IDL compiler, regardless of the - value of the -Ge flag.</td> + + <td>If the value of the flag is 0, tao_idl will generate code that + will use native C++ exceptions. If the value of the flag is 1, + tao_idl will generate code that will use the <CODE>CORBA::Environment</CODE> variable for + passing exceptions. If the value of the flag is 2, the C++ 'throw' keyword will be used + in place of ACE_THROW_SPEC, ACE_THROW, and ACE_RETHROW (ACE_THROW_RETURN and + TAO_INTERCEPTOR_THROW will still be used). The default depends on how TAO_IDL + has been built. If TAO_IDL is built with native exceptions enabled, the IDL + compiler will not generate the emulated exception macros. If IDL compiler is + built with native exceptions disabled, macros would be generated by default. </td> + <td> </td> </tr> <tr><a name="Gp"> @@ -678,9 +664,9 @@ also receives other options that are specific to it.<p> <td>Generate uninlined constant if defined in a module</td> <td>Inlined (assigned a value in the C++ header file) by default, but this causes a - problem with some compilers when using pre-compiled headers. Constants declared - at global scope are always generated inline, while those declared in an interface - or a valuetype never are - neither case is affected by this option.</td> + problem with some compilers when using pre-compiled headers. Constants declared + at global scope are always generated inline, while those declared in an interface + or a valuetype never are - neither case is affected by this option.</td> </tr> <tr> |