Report 0342 Actions
Problem Report Number |
0342 |
Submitter's Classification |
Specification problem |
State |
Resolved |
Resolution |
Permanent Interpretation (PIN) |
Problem Resolution ID |
PIN.X.0058 |
Raised |
1997-07-07 08:00 |
Updated |
2003-03-13 08:00 |
Published |
1997-07-10 08:00 |
Product Standard |
Internationalised System Calls and Libraries (XPG4) |
Certification Program |
The Open Brand certification program |
Test Suite |
VSX4 version 4.3.5 |
Test Identification |
POSIX.os/devclass/tcgetattr 3 |
Specification |
System Interfaces and Headers Issue 4 |
Location in Spec |
See Problem Text |
Linked Problem Reports |
TIN4.011, (in, old, system) |
Problem Summary |
PIN4.058 There is a conflict between the X/Open and POSIX mode of Operation for this test case. If an implementation does not support split baud rates, then XPG4 mandates that the input baud rate stored in the... |
Problem Text |
**********************************************************************
There is a conflict between the X/Open and POSIX mode of Operation for this test case. If an implementation does not support split baud rates, then XPG4 mandates that the input baud rate stored in the termios structure be equal to zero, while POSIX.1 allows for both zero or the output rate.
According to the test strategy an implementation can either be POSIX.1 conformant or XPG4, but not both. This cannot be right.
X/OPEN CAE Specification, System Interfaces and Headers, Issue 4, on tcgetattr, page 457 stated:
"If the terminal device does not support split baud rates, the input baud rate stored in the termios structure will be zero."
POSIX-Part 1: System Application Program Interface (API), IEEE std 1003.1 first edition 1990-12-07, Section 7.2.1.2, page 143,
and
POSIX-Part 1: System Application Program Interface (API), Ammendment 1: Realtime Extension (C Language) IEEE std 1003.1b -1993, Section 7.2.1.2 page 183 stated:
"If differing baud rates are not supported, the rate returned as the output baud rate shall be the actual baud rate. The rate returned as the input baud rate shall be either the number zero or the output rate (as one of the symbolic values). Permitting either behavior is obsolescent. 3)."
and down in the POSIX.1 notes sestion:
3) In a future revision of this standard, a returned value of zero as the input baud rate when differing baud rates are not supported may no longer be permitted.
Our implementation does not support split baud rates. We have always chosen to return the output baud rate, and have always been XPG4 branded and POSIX.1 certified. Up to until VSX4.3.4 both behaviors were allowed in XPG4 mode and should not have been changed in VSX4.3.5. Specially that the future POSIX direction will no longer permit the return of zero.
**********************************************************************
|
Test Output |
*********************************************************************** /tset/POSIX.os/devclass/tcgetattr/T.tcgetattr 3 UNREPORTED
Test Description: If general terminal interface supported: If the implementation supports input and output baud rates that differ: The baud rates stored in the termios structure returned by the tcgetattr() reflect the actual baud rates even when they are equal Otherwise The output baud rate stored in the termios structure returned by the tcgetattr() reflect the actual baud rate. The input baud rate stored in this termios structure is equal to zero. In POSIX mode the input baud rate may also equal the actual baud rate. This test is not executed in XPG3 mode. Posix Ref: Component TCGETATTR Assertion 7.2.1.2-05(C)
Test Information: tcgetattr() did not return correct input baud rate when input = output expected 0, observed 9600 ***********************************************************************
|
Review Information
Review Type |
TSMA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Recommendation |
No Resolution Given |
Review Response |
|
Review Type |
SA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
No Resolution Given |
Review Conclusion |
Agreed to upgrade temporary interpretation TIN4.011 to a permanent interpretation.
|
Review Type |
SA Review |
Start Date |
null |
Completed |
null |
Status |
Complete |
Review Resolution |
Permanent Interpretation (PIN) |
Review Conclusion |
A Permanent Interpretation is granted.
|
Problem Reporting System Options:
|