5 @page IDL Inherited Operation Test README File
7 This test checks that an IDL compiler bug, fixed by
9 Fri Mar 20 16:04:58 UTC 2009 Jeff Parsons <j.parsons@vanderbilt.edu>
11 never gets re-introduced. The IDL declarations that caused the
14 - A base interface, with an operation, is declared inside 2
16 - The nested modules are closed.
17 - The nested modules are reopened, and forward declaration of
18 the base interface appears inside.
19 - The nested modules are closed.
20 - The outer module is reopened, and a derived interface
21 declaration appears inside, using the partially scoped
22 name of the base interface.
24 This type of IDL caused the base interface operation to be missing
25 from the operation table in generated code for the derived
26 interface. Client calls to this operation on a derived object
27 would result in a BAD_OPERATION exception.
29 The test is here instead of in the IDL_Test directory because
30 the bug can be detected only at runtime, by a remote call.
31 IDL_Test is designed to catch only:
33 - Error messages incorrectly caused by legal IDL
34 - Errors from incompilable generated code
35 - Incorrect repository IDs, fetched by a local stub call
37 To run the test use the run_test.pl script:
41 the script returns 0 if the test was successful.