Known Problems and Bugs
-----------------------

Most of these deal with problems in Orbix 1.3, and may not be present
on other platforms.

An invalid object reference string will result in a segmentation
violation and core dump in Orbix 1.3.  This is really a problem in
Orbix's string_to_object() code and will not be fixed in tclIR to
increase portability.

If user defined structures or sequences are used, the client stubs
generated by the IDL compiler (with the -A switch) must be linked into
the TclIR executable.  This is a VERY inconvenient and will hopefully
be fixed in a future release of Orbix.

Currently inout and out parameters are not supported in method
invocations mostly because we don't use them.  I will probably add
these in the next month so that the implementation is more complete.

Currently unions, arrays, octets, typecodes, principals, and anys are
the only unsupported types in tclIR.  I will probably add support for
these as well for completeness.

Sequences and strings are not checked for their IDL defined upper bound
limits.

There are problems with using nested types that seem to mostly stem
from problems in the the _create_request() call (or possibly my
understanding of the IR).  This problem will be fixed soon because it
has forced us to make all of our types global which we not really want
to do.

Undoubtedly there are memory leaks.  I will Purify it before the next
release.


