1.3 Terms and abbreviations
This table defines some terms and abbreviations that are commonly used in the Iris documentation, or have a meaning that is Iris-specific:
||Short for if and only if.
||Inter-Process Communication, either on the same host, for example
TCP or pipes, or on different hosts, for example TCP.
||Dynamic Shared Object (
*.so) or DLL.
||Remote Procedure Call protocol using JSON.
||Binary JSON variant that is based on arrays of 64-bit values. It is defined in 3.5 U64JSON.
||A piece of software with well-defined abstract interfaces that
represents a piece of hardware or other functionality.
||Sometimes used as a synonym for component or instance but generally avoided in this document.
||An entity that provides functionality to other instances, or uses
functionality that is provided by other instances, or both. For
example, components, debuggers, clients, and plug-ins are all
||Any event that is produced by an instance. This might be a trace
event, for example
INST for each executed
instruction, a simulation event, for example
IRIS_BREAKPOINT_HIT, or any other kind of
event. Clients can observe events upon request.
||An interface for debug and trace. Not an abbreviation or