Deprecate classes OSHostent, OSProtoent, and OSServent
Reason for change
There are 2 versions of these classes on Windows – OSHostent, OSProtoent, and OSServent in the WindowsPlatformFunctions subapplication and OSHostEnt, OSProtoEnt, and OSServEnt in the SocketCommunicationsInterface application. There are no references to the OSHostent, OSProtoent, or OSServent classes.
Change
The OSHostent, OSProtoent, and OSServent classes are moved from the WindowsPlatformFunctions subapplication to the WindowsObsoletePlatformInterface subapplication. Extensions to these classes are moved from the WindowsPlatformAccessors subapplication to the WindowsObsoletePlatformInterface application also.
The OSHostEnt, OSProtoEnt, and OSServEnt classes are moved from the SocketCommunicationsInterface application to both the SciComWIN and SciCommUNIX subapplications since there are minor differences in the layout of the structures represented by these classes on Windows and UNIX.
The SciHostEnt, SciProtoEnt, and SciServEnt classes are moved from the SciComWIN subapplication to the SocketCommunicationsInterface applications since they are the same on both Windows and UNIX. These classes are removed from the SciComUNIX subapplication.
Action required
If your applications have any references to the OSHostent, OSProtoent, or OSServent classes, you should add the SocketCommunicationsInterface application to the prerequisites of your application; change the class references to OSHostEnt, OSProtoEnt, or OSServEnt; and adapt your application to use the accessor methods of these classes.
Last modified date: 04/05/2019