Technical data

Callback functions for sockets - Windows platforms
466
-
VHDL Foreign Language Interface and Verilog PLI ModelSim EE/PLUS Reference Manual
mti_GetTopRegion
Gets the first top-level module. Use mti_NextRegion to get additional top-level modules.
mti_GetPrimaryName
Gets the module name.
mti_GetSecondaryName
Returns NULL for Verilog modules.
The following functions operate on Verilog instances in the same manner that they
operate on VHDL instances:
All other functions only operate on VHDL instances and objects. Specifically, the
functions that operate on VHDL signals and drivers cannot be used on Verilog
nets and drivers. For example, a call to mti_FirstSignal on a Verilog region always
returns NULL. You must use the PLI functions in "Using the Verilog PLI" (p483)
to operate on Verilog objects.
Callback functions for sockets - Windows platforms
Under Windows, sockets are separate objects from files and pipes, which require
the use of different system calls. There is no way to determine if a given descriptor
is for a file or a socket. This necessitates the use of different callback functions
for sockets in order to make this work under Windows NT/95/98. The following
functions work specifically with sockets. While these functions are required for
use with Windows, they are optional for use on UNIX platforms.
• mti_AddSocketInputReadyCB (p468)
• mti_AddSocketOutputReadyCB (p468)
mti_CreateRegion (p469) mti_GetRegionFullName (p473)
mti_FindRegion (p471) mti_GetRegionName (p473)
mti_FirstLowerRegion (p471) mti_GetRegionSourceName (p473)
mti_GetCurrentRegion (p472) mti_HigherRegion (p475)
mti_GetLibraryName (p472) mti_NextRegion (p476)