Please report new issues athttps://github.com/DOCGroup
See 1.11 of the C++ mapping (03-06-03). Described the fixed datatype which isn't supported by TAO. For example: typedef fixed <5,2> F; interface A { void op (in F arg) };
Known problem. There's never been any real demand for the "fixed" IDL data type which is why it has never been implemented. Note that TAO does support the tk_fixed TypeCode, meaning that it can receive Anys containing "fixed" values. It just won't be possible to extract the value from that Any.
accept
changed priority
Supporting the fixed type is important because - JacORB supports fixed and interoperability between Tao and JacORB is broken for IDLs that use fixed - fixed is important for business applications because BCD (http://en.wikipedia.org/wiki/Binary-coded_decimal) is important for those applications - BCD is used in COBOL (see the COBOL Language Mapping 1.6 Mapping for Fixed Types) (incidentally COBOL uses the same in-memory representation for PACKED-DECIMAL as IIOP for fixed, or is this by design?) - fixed is part of the standard and Tao is not standard-conforming without fixed I do not believe that the implementation would be difficult. There are lots of number conversion constructors and operators, but this should not be difficult. As for converting to IIOP, one could start with the hack of converting the fixed to an (integer) string, then fill each half-byte with one position of the string (see 15.3.2.8 Fixed-Point Decimal Type of the Core Specification). "-123456" -> 0x0123456C Actually, I just checked org.jacorb.orb.CDROutputStream.write_fixed(final java.math.BigDecimal value) it does exactly this, toString() and write out the digits. (Hope that looking at JacORB's sources is not a breach of copyright).
testing comments