Any change (either to the case conventions, or to align the names with the conventions) will cause some applications to experience portability problems at compilation time. Bearing in mind that a portability problem exists with the specification in it's current state, it has been decided to align the names with the stated case conventions (all upper case).
It is strongly recommended that applications using mixed case naming are changed to conform to the stated case conventions. .
If it is desired to guarantee their applications portability across different implementations of this version of the XMS specification it is recommended that the following defines are included in an application after inclusion of the <xms.h> header file.
In the X/Open X.400 (C316) and XDS (C317) Issue 2 CAE specifications, this constraint is expressed in terms of the number of elements in a string, rather than the number of octets.
In addition, the XOM Issue 2 API (C315) Appendix A: "Differences from IEEE Standard" section A.2 highlights this item and states:
The IEEE 1224-1993 Standard incorrectly introduced the "number of octets" definition. This is the subject of an IEEE interpretations request, and a published IEEE interpretation (reference IRQ# IEEE1224-1993/1, copy in XoTGnet 4687) states that "number of elements" is right and "number of octets" is wrong.
This CR proposes to replace the statement in XMS with text derived from that which appears in the X/Open X.400 and XDS Issue 2 specifications on this item.
Note:
The number of octets used to represent a string with multibyte characters (for example, T.61 Teletext) may exceed the number of characters expressed in the value length constraint. Therefore the length field of such a string (which gives the number of octets by which it is represented) may exceed the value length constraint.
If you can't find the information you need, please contact X/Open at any of its offices.
Copyright X/Open Company Limited, © 1995