- Notes about X-Midas messages:
  - NeXtMidas does not deal with "configured" and "unconfigured" messages the same way X-Midas does.
    - In NeXtMidas messages, the data can be any object (frequently a Table) without any specific configuration.
    - X-Midas messages are structured byte buffers that either match a pre-defined configuration (configured) or are defined ad hoc (unconfigured).

X-Midas Users Take Note:
Since host primitives are unable to handle NeXtMidas ID's (which are strings) all messages from a host primitive will be sent to the same location as specified by the `/MSGID=` switch passed to the host primitive. By default `/MSGID=` is set to null, to see the messages in the `processMessage` procedure of a macro use `/MSGID=MAIN`. (This applies to XBC only, not NeXtOpt.)