HP-UX Reference (11i v3 07/02) - 2 System Calls (vol 5)

getsockopt(2) getsockopt(2)

passing a size_t pointer will evoke compile-time warnings, which must be corrected in order for the

application to behave correctly. Applications that use socklen_t

now, where appropriate, will avoid

such migration problems. On the other hand, applications that need to be portable to the UNIX 95 proﬁle

should follow the X/Open speciﬁcation (see xopen_networking(7)).

WARNINGS

Linking binary objects compiled to X/Open Sockets speciﬁcation and binary objects compiled to HP-UX

BSD Sockets speciﬁcation to the same executable may result in unexpected behavior, including application

abnormal termination and unexpected socket errors. See xopen_networking(7) for details and remedy.

FUTURE DIRECTION

Currently, the default behavior is the HP-UX BSD Sockets; however, it might be changed to X/Open

Sockets in a future release. At that time, any HP-UX BSD Sockets behavior that is incompatible with

X/Open Sockets might be obsoleted. Applications that conform to the X/Open speciﬁcation now will avoid

migration problems (see xopen_networking(7)).

AUTHOR

getsockopt() and setsockopt() were developed by HP and the University of California, Berkeley.