This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.Questions on this system should be addressed to the Conformance Statement Manager at The Open Group.
Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.
A product may be registered in all members of a binary-compatible family of products on the basis of a single test report.
Answer the questions for each binary-compatible family. Alternatively, provide the answers in the Appendix at the end of this document or if lengthy provide a separate external html file to The Open Group that can be linked into the Appendix.
Question 1: Which of the following XSI Option Groups are supported by the implementation?
Response
Support for an XSI Option Group can only be claimed if all interfaces in that group behave according to the relevant descriptions in System Interfaces, Issue 6.
If an implementation does not support an Option Group then the system need not support the functions or functional behavior.
Rationale
Base Definitions, Issue 6 states that the system may provide one or more of the XSI Option Groups listed.
Reference
Technical Standard, Base Definitions, Issue 6, Section 2.1.4, XSI Conformance and Section 2.1.5, Option Groups.
Internationalized System Calls and Libraries Extended V3 Product Standard.
Question 2: Which of the following options are supported by the implementation?
Support for these options enables additional semantics for interfaces as described in the relevant descriptions in System Interfaces, Issue 6.
The system may provide support for additional options beyond those required for XSI conformance or covered by the XSI Option Groups.
Technical Standard, Base Definitions, Issue 6, Section 2.1.4, XSI Conformance and Section 2.1.6, Options.
Question 3: For each of the symbolic constants, specified in the <unistd.h> header file, are the associated features always available on the system?
Where indicated in the following table, select one of the options given (either "Yes" or "Variable"). Select "Variable" if there are system dependent or file_system dependent configuration procedures that can remove or modify any or all of these features.
If any of the above are Variable, describe in the area below the manner in which variations occur.
For a conformant implementation, these POSIX features must be provided. In some cases the feature need not be provided for all files or devices supported by the implementation.
Technical Standard, Base Definitions, Issue 6, Chapter 13, Headers, <unistd.h>.
Question 4: What are the values associated with the following constants specified in the <float.h> header file?
This set of constants provides useful information regarding the underlying architecture of the implementation.
Technical Standard, Base Definitions, Issue 6, Chapter 13, Headers, <float.h>.
Question 5: What are the values associated with the following constants (optionally specified in the <limits.h> header file)?
Each of these limits can vary within bounds set by the Base Definitions, Issue 6. The minimum permitted value is specified in Chapter 13, <limits.h>.
Technical Standard, Base Definitions, Issue 6, Chapter 13, Headers, <limits.h>.
Question 6: What are the values associated with the following constants specified in the <limits.h> header file?
For each line in the table below, add the minimum and maximum values for your implementation. These values may be stated to be "Unlimited" if your implementation does not impose a limit. The minimum should be the smallest value that is returned from sysconf(), pathconf(), or fpathconf(), or as defined in <limits.h>. The maximum value should be the largest value that is returned from sysconf(), pathconf(), or fpathconf(). Macro NameMeaningMinimumMaximum BC_BASE_MAX Maximum ibase and obase values allowed by the bc utility. BC_DIM_MAX Maximum number of elements permitted in an array by the bc utility. BC_SCALE_MAX Maximum scale value allowed by the bc utility. BC_STRING_MAX Maximum length of a string constant accepted by the bc utility. CHARCLASS_NAME_MAX Maximum number of bytes in a character class name. COLL_WEIGHTS_MAX Maximum number of weights that can be assigned to an entry of the LC_COLLATE order keyword in the locale definition file. EXPR_NEST_MAX Maximum number of expressions that can be nested within parentheses by the expr utility. LINE_MAX Maximum length in bytes including the trailing newline of a utility's input line when the utility is described as processing text files. NGROUPS_MAX Maximum number of simultaneous supplementary group IDs per process. RE_DUP_MAX Maximum number of repeated occurrences of a regular expression permitted when using interval notation.
Each of these limits can vary within bounds set by the Base Definitions, Issue 6. The minimum value that a limit can take on any conforming system is given in the corresponding _POSIX_ or _POSIX2_ value. A specific conforming implementation may provide a higher minimum value than this and the maximum value that it provides can differ from the minimum. Some conforming implementations may provide a potentially infinite value as the maximum, in which case the value is considered to be indeterminate. The minimum value must always be definitive since the _POSIX_ or _POSIX2_ value provides a known lower bound for the range of possible values.
Question 7: What are the values associated with the following numerical constants specified in the <limits.h> header file?
Question 8: What are the values associated with the following numerical constants specified in the <stdio.h> header file?
This set of constants provides useful information about the implementation.
Technical Standard, Base Definitions, Issue 6, Chapter 13, Headers, <stdio.h>.
Question 9: Which of the following option errors, ( denoted by "may fail" within the specification ), listed in System Interfaces, Issue 6 are detected in the circumstances specified?
Select Yes or No. For functions marked with an asterix, there are additional family members with the suffices, f and l. If the error handling is different for those please add details in the Appendix at the end of this questionnaire.