Please report new issues athttps://github.com/DOCGroup
TAO type codes have been generated by the IDL compiler from the beginning as a hard-coded array of longs. Since those days, 2-byte values have crept into the type code spec, notably the valuetype-related items ValueModifier and Visbility. If the TypeCode class methods read them as 4-byte quantities, we are incompatible with type codes from other ORBs. If we read them as 2-byte quantities, we get alignment errors reading our own type codes. TAO's implementation of type codes is slated for overhaul soon, so this bug is being marked as dependent on 1769, which includes type code overhaul, among other things.
Sorry, the dependency is actually on 1637.
A report on this bug (the part about non-interoperability with other ORBs) was made recenly by Hakim Souami <hakim dot souami at fr dot thalesgroup dot com>. He has been added to the CC list.
Mine.
TAO 1.4.5's new TypeCode implementation addresses this bug.