Multiple Imports

IPL allows multiple FIX library imports, but this can introduce side effects and ambiguity.

Declaring multiple imports

import FIX_4_2
import FIX_4_4
 
message OrderSingle {
  req Side
}
 
message FIX_4_4.ExecutionReport {
  req Side
  req PeggedPrice
}

If a message exists in both libraries and is unqualified, IPL can emit an ambiguity warning.

Side effects to be aware of

Union of enum cases and record fields

With multiple imports, available enum cases can become the union from both library versions.

Field-name/tag consistency nuances

If two libraries provide same tag with different field names, import order influences conflict resolution in custom declarations.

For example, declaring:

record myRecord {
  IDSource "22" : IDSource
}

may be accepted while a different same-tag name can fail, depending on import order.

See also Libraries.