ANSI INCITS ISO IEC 14366-1996 Information technology - Test methods for measuring conformance to Open Systems Interconnection (OSI) abstract data manipulation C language interfaceP.pdf

《ANSI INCITS ISO IEC 14366-1996 Information technology - Test methods for measuring conformance to Open Systems Interconnection (OSI) abstract data manipulation C language interfaceP.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS ISO IEC 14366-1996 Information technology - Test methods for measuring conformance to Open Systems Interconnection (OSI) abstract data manipulation C language interfaceP.pdf（70页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL STANDARD ISO/IEC 14366 First edition 1996-06-01 Information technology - Test methods for measuring conformance to Open Systems Interconnection (03) abstract data manipulation C language interfaces - Binding for Application Program Interface (API) Technologies de /information - MBthode

2、s dessaipour mesurer la conformit aux interfaces de langage C pour la manipulation de don FAX: +1202 728-9614. Introduction vii INTERNATIONAL STANDARD OISO/IEC ISO/IEC 14366:1996(E) 1 Information technology-Test methods for 2 measuring conformance to Open Systems 3 Interconnection (OSI) abstract dat

3、a 4 manipulation C language 5 interfaces-Binding for Application Program 6 Interface (API) 7 8 9 This International Standard defines requirements for test methods for measuring 10 conformance to ISO/IEC 14364 (41.” 11 ISO/IEC 14364 (4) contains a programming language binding specification for 12 ISO

4、/IEC 14360 2), using the C programming language. ISO/IEC 14362 (3) con- 13 tains language-independent requirements for test methods for measuring confor- 14 mance to programming language binding specifications for ISO/IEC 14360 2), 15 such as that contained in ISO/IEC 14364 (4). This International S

5、tandard con- 16 tains C language specific requirements for the test methods. Taken in conjunction 17 with the requirements imposed by ISO/IEC 14362 3), they constitute the require- 18 ments that shall be satisfied by test methods used for measuring conformance to 19 ISO/IEC 14364 (4). Section 1: Gen

6、eral 1.1 Scope 20 1) The numbers in curly brackets correspond to those of the references in 1.2. 1.1 Scope ISOLCJX 14366:1996(E) OISO/IEC 21 The following standards contain provisions which, through reference in this text, 22 constitute provisions of this International Standard. At the time of publi

7、cation, 23 the editions indicated were valid. All standards are subject to revision, and parties 24 to agreements based on this International Standard are encouraged to investigate 25 the possibility of applying the most recent editions of the standards indicated 26 below. Members of IEC and IS0 mai

8、ntain registers of currently valid Interna- 27 tional Standards. 28 29 30 31 32 33 34 35 36 (41 ISOIIEC 14364: 1996, Information technology-Open Systems Interconnec- 37 tion (OSI) abstract data manipulation C language interfaces-Binding for 38 Application Program Interface (API). 39 40 41 42 A set o

9、f test methods that conforms to this International Standard shall conform to 43 IEEE Std 1003.3-1991 151, with references to the “P0SIX.n test method 44 specification” being interpreted as references to this International Standard, and 45 references to “the POSIX standard for which conformance is be

10、ing measured” being 46 interpreted as references to ISO/IEC 14364 (4). 47 48 49 50 51 52 A set of test methods that conforms to this International Standard shall also con- 53 form to ISO/IEC 14362 31. 1.2 Normative References 111 ISO/IEC 9899: 1990,2 Programming languages-C. Ia ISO/IEC 14360: 1996,

11、I f n ormation technology-Open Systems Interconnec- tion (OSI, abstract data manipulation-Application Program Interface (API) Language independent. 131 ISO/IEC 14362: 1996, I n ormation technology-Test methods for measuring f conformance to Open Systems Interconnection (OSI) abstract data manipulati

12、on-Application Program Interface (API) Language indepen- dent. (51 IEEE Std 1003.3-1991,3 IEEE Standard for Information Technology-Test Methods for Measuring Conformance to POSIX. 1.3 Conformance In addition to meeting the conformance criteria defined in IEEE Std 1003.3-1991 51, a set of test method

13、s that conforms to this International Standard shall test all documentation assertions defined in this International Standard. NOTE: Conformance to IEEE Std 1003.3-1991 (51 implies that the test methods will test all other assertions defined in this International Standard. 54 2) ISO/IEC documents ca

14、n be obtained from the IS0 Central Secretariat, 1 Rue de Varembe, Case 55 Postale 56, CH-1211, Geneve 20, SwitzerlandDuisse. 56 3) IEEE documents can be obtained from the IEEE Service Center, 445 Hoes Lane, P.O. Box 1331, 57 Piscataway, NJ, 08855-1331, USA. 2 1 General 0 ISOAEC ISO/IEC 14366:1996(E)

15、 2 3 2.1.1 General and Typographic Conventions 8 9 10 11 12 13 14 15 The C language binding specifies C identifiers for all the elements of the interface. 16 These elements include function names, typedef names, and constants. All the C 17 identifiers are mechanically derived from the language-indep

16、endent names. 18 The interface uses part of the C public namespace for its facilities. All identifiers 19 that start with the letters om, o See 003(A) in 55.1 R02 The symbolic constant OM-FALSE) represents false, which is equal to zero. See 003(A) in 5.5.1 R03 008(A) The symbolic constant (OM-TRUE r

17、epresents true and is equal to the integer one. See 003(A) in 5.5.1 The value true is denoted by any integer other than zero. 28 5.2.3 Descriptor 29 30 31 32 33 34 35 36 R04 The structure OM-descriptor-struct is declared as follows: typedef struct OM-descriptor-struct 1 OM-type type; OM-syntax synta

18、x; OM-value value; OM-descriptor; See 003(A) in 5.5.1 37 38 39 40 41 GAO1 For funct0 in om-copy 0, om-create(), om-decode(), om-encode(), om_get(): 42 43 44 45 46 GAO2 For funct0 in om-copy(), om-create(), om-decode(), om-encode(), omxet(): 47 48 009(A) The macro OMJXNTAX extracts the syntax value f

19、rom an OM-descriptor-struct. 49 50 010(A) The macro OM-SYNTAX-ASSIGN stores a syntax value in an OM-descriptor-struct. When funct0 is called and returns successfully, then the type member of any OM-descriptor-struct returned identifies the type of the attribute value. When funct() is called and retu

20、rns successfully, then the syntax member of any OM-descriptor-struct returned identifies the syntax of the attribute value. 18 5 Test Assertions-Service Interface 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 OI

21、SO/IEC ISOLIEC 14366:1996(E) GAO3 For funct() in om-copy(), om-create(), om-decode(), om-encode(), om_get(): When funct0 is called and returns successfully, then the (OM-S-LONG-STRING) value of any descriptor returned is tOM_TRUE) if, and only if, the descriptor is service generated and the length o

22、f the value is greater than an implementation defined limit. DO2 The limit that, when exceeded by the length of a descriptor value, causes the OMSLONGSTRING) component of the syntax com- ponent of the descriptor to be set to (OM-TRUE) is documented. GAO4 For funct() in om-copy(), om-create(), om-dec

23、ode(), om-encode(), om_get(): When funct( is called and returns successfully, then the (OM-S-NO-VALUE) value of any descriptor returned is (OM-TRUE) only if the descriptor is service generated and the value is not present. GAO5 For funct() in om-copy(), om-create(), om-decode(), om-encode(), om_get(

24、): When funct( is called and returns successfully and the Syntax is String(*), then the (OM-S-LOCAL-STRING) value of any descriptor returned is (OM-TRUE) if, and only if, the string is represented in an implementation defined local character set. DO3 GAO6 Any implementation-defined local character s

25、ets are documented. For funct() in om-copy(), om-create(), om-decode(), om-encode(), omxe to: When funct( is called and returns successfully, then the (OM-S-SERVICE-GENERATED) value of any descriptor returned is (OMTRUE) if, and only if, the descriptor is service generated and the first descriptor o

26、f a public object, or the defined part of a private object. GAO7 For funct() in om-copy(), om-create(), omdecode(), om-encode(), om_get(): When funct( is called and returns successfully, then the (OM-S-PRIVATE) value of any descriptor returned is true if, and only if, the descriptor in the service-g

27、enerated public object contains a reference to the handle of a private subobject, or is the defined part of a private object. GAO8 For funct() in om-copy(), om-create(), om-decode(), om-encode(), om_get(): When funct() is called and returns successfully, then the value member of any OM-descriptor-st

28、ruct returned contains the attribute value. R05 (OMSLONGSTRING), OMJ3_NO_VALUE), (OMSLOCALSTRING) , (OMSSERVICEGENERATED) , and (OM-S-PRIVATE) are encoded in the high order bits of the syntax 5.2 Datatypes 19 ISOLIEC 14366:1996(E) OISO/lEC 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111

29、112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 GAO9 R06 011(A) GA10 012(A) R07 GA11 013(A) 014(A) R08 GA12 structure member. (See GAO9 in 5.2.3, GA10 in 5.2.3, GA11 in 5.2.3, GA12 in 5.2.3, and GA13 in 5.2.3.) For finct() in om-copy(), om-createt), omdeco

30、de(, om-encode(), omzet(): When funct( is called and returns successfully, then OM-S-LONG- STRING) is represented by bit 15 (0x8000) of the syntax member of any OM-descriptor-struct returned. The (OMSLONGSTRING) component of the syntax structure member is represented by the constant (OM-S-LONG-STRIN

31、G). See 010(A) in 5.5.1 The macro OMJS-LONG-STRING tests the (OMSLONGSTRING) bit of an OM-descriptor-struct and returns OM-TRUE) if it is set. For funct() in om-copy(), om-create(), omdecodeo, om-encode(), omxet(): When funct() is called and returns successfully, then OM-S-NO-VALUE) is represented b

32、y bit 14 (0x4000) of the syntax member of any OM-descriptor-struct returned. The macro OM-IS-NO-VALUE tests the (OM-S-NO-VALUE) bit of an OM-descriptor-struct and returns OM-TRUE) if it is set. The OM-S-NO-VALUE) component of the syntax structure member is represented by the constant (OM-S-NO-VALUE)

33、. See 010(A) in 5.5.1 For funct( in om-copy(), om-create(), om-decode(), om-encode(), om-get(): When funct( is called and returns successfully, then the OM-S-LOCAL-STRING) is represented by bit 13 (0x2000) of the syntax member of any OM-descriptor-struct returned. The macro OMISLOCALSTRING tests the

34、 (OM-S-LOCALSTRING) bit of an OM-descriptor-struct and returns OM-TRUE if it is set. The macro OMSETLOCALSTRING sets (OM-SWLOCALSTRING bit of an OM-descriptor-struct. the The Local-String component of the syntax structure member is represented by the constant (OMSLOCAISTRING). See 010(A) in 5.5.1 Fo

35、r finct() in om-copy(, om-create(), om-decode(), om-encode(), om_get(): When funct() is called and returns successfully, then OM-S-SERVICE-GENERATED) is represented by bit 12 (0x1000) of the syntax member of any OM-descriptor-struct returned. 20 5 Test Assertions-Service Interface 135 136 137 015(A)

36、 The macro OMJS-SERVICE-GENERATED tests the (OM-S-SERVICE-GENERATED) bit of an OM-descriptor-struct and returns (OM-TRUE) if it is set. 138 139 140 141 142 143 144 145 146 147 148 149 150 R09 The Service-Generated component of the syntax structure member is represented by the constant (OM-S-SERVICE-

37、GENERATED). See 010(A) in 5.5.1 GA13 For funct0 in om_copyO, om-createo, om-decode(), om-encodeo, omxet(): When funct( is called and returns successfully, then (OM-S-PRIVATE is represented in the C interface by bit 11 (0x0800) of the syntax member of any OM-descriptor-struct returned. 016(A) RlO The

38、 macro OM-IS-PRIVATE tests the (OM-S-PRIVATE) bit of an OM-descriptor-struct and returns (OM-TRUE) if it is set. The Private component of the syntax structure member is represented by the constant OM-S-PRIVATE). See 010(A) in 5.5.1 151 5.2.4 Enumeration 152 153 154 Rll The datatype OM-enumeration is

39、 declared as follows: typedef OM-sint32 OM-enumeration; See 003(A) in 5.5.) 155 5.2.5 Exclusions 156 157 158 R12 The datatype OM-exclusions is declared as follows: typedef OM-uint OM-exclusions; See 003(A) in 5.5.) 159 NOTE: There are no further assertions relating to this type, as no data of this t

40、ype 160 is generated by the interface. OISO/IEC ISOAEC 14366:1996(E) 5.2 Datatypes 21 ISOAEC 14366:1996(E) OISO/IEC 5.2.6 Integer 161 162 163 R13 The datatype OM-integer is declared as follows: typedef OM-sint32 OM-integer; See 003(A) in 5.5.1 164 5.2.6.1 Modification 165 166 167 168 169 R14 The dat

41、atype OM-modification is declared as follows: typedef OM-uint OM-modification; See 003(A) in 5.5.1 NOTE: There are no further assertions relating to this type, as no data of this type is generated by the interface. 170 5.2.7 Object 171 172 173 174 175 176 177 178 179 R15 The structure OM-object is d

42、eclared as follows: typedef struct OM-descriptor-struct *OM-object; See 003(A) in 5.5.1 R16 For finct0 in om-copy0, om_createO, om-decode0, om-encode(), omset(): When funct( is called and returns successfully, then any data value returned of the datatype OM-object is an ordered sequence of one or mo

43、re instances of the Descriptor datatype. See GA14 in 5.2.9,021(A) in 5.2.10.1 180 5.2.8 Object Identifier 181 182 183 R17 The datatype OM-object-identifier is declared as follows: typedef OM-string OM-object-identifier; See 003(A) in 5.5.1 184 NOTE: There are no further assertions relating to this t

44、ype, as no data of this type 185 is generated by the interface. 22 5 Test Assertions-Service Interface 186 187 188 189 190 191 192 193 194 195 196 The macros OMIMPORT(cZassname) and OMIMPORT(OIDname) make the class or other Object Identifier constants, respectively, available within a compilation un

45、it. 018(A) The macros OM-EXPORT(cZass-name) and OMEXPORT(OIDname) allocate the memory for the constants that represent the class or other Object Identifier, respectively. 019(A) The macro OM-OID-DESC(type,OlD_name) initializes a descriptor: the type component is set to the given type, the syntax com

46、ponent is set to OMSOBJECTIDENTIFIERSTRING, and the value com- ponent is set to the given OID-name. 020(A) The macro OM-NULL-DESCRIPTOR initializes a descriptor to mark the end of a client-allocated public object. 197 5.2.9 Private Object 198 199 200 201 202 203 204 205 206 207 208 209 5.2.10 Public

47、 Object 210 211 212 213 021(A) When om-get( is called and returns successfully, then the data value 214 returned of the datatype OMgubZic-object is a public object that 215 comprises one or more descriptors. 216 022(A) When omxet() is called and returns successfully, and the data value 217 returned

48、of datatype OM_pubZic-object has descriptors for a particu- 218 lar attribute having two or more values, then the descriptors are adja- OISOiIEC ISOKEC 14366:1996(E) 017(A) R18 The datatype OMgriuate-object is declared as follows: typedef OM-object OM_private-object; See 003(A) in 5.5.1 GA14 For fun

49、ct( in om-copy0, om-creuteo, om-decodeo, om-encode0 When funct( is called and returns successfully, then any data value returned of the datatype OM_priuute-object is a designator or handle for a private object that comprises a single descriptor whose Type component is private-object. R19 The OM-S-SERVICE-GENERATED) and OM-S-PRIVATE) bits in the syntax component are always set by the service. See GAO6 in 5.2.3, GAO7 in 5.2.3.1 R20 The datatype OMgubZic-object is declared as follows: typedef OM-object OM_publ