Skip to main content

erCannotImport

erCannotImport = 1

Example​

function IsImportBindingFailure(const ErrorType: TIFException): Boolean;
begin
  Result := ErrorType = erCannotImport;
end;

Usage​

erCannotImport indicates that the Velox scripting loader could not bind a compiled external procedure to an available Velox operation.

Formatting and exception state​

ExceptionToString returns Cannot Import followed by the safe prefix of Param. Velox scripting's SafeStr stops immediately before the first control character from #0 through #31; a line break, tab or NUL therefore hides the remainder of the diagnostic. ExceptionParam still represents the saved parameter rather than the formatted/truncated result.

Additional Technical Info​

erCannotImport is member ordinal 1 of TIFException, the script-visible declaration that is kept in exact ordinal alignment with PascalScript's runtime TPSError. Its sidebar position 18 is alphabetical navigation metadata and is not its enumeration value.

erCannotImport identifies failure to resolve an external procedure recorded in compiled PascalScript bytecode. “Import” here means binding the bytecode declaration to a function already registered in the current script executor; it does not perform a network request, load a Velox module, or search the operating system dynamically. The loader emits this category while reading an external procedure record. It first tries the procedure name; when the compiled record contains no name, it reports the declaration text instead. A failed binding stops LoadData, releases the partially loaded type/procedure/variable structures, and leaves the error available to the owning execution boundary.

Behavior, recovery and quirks​

  • The error usually points to a compiler/Velox availability mismatch: a function, method or declaration was available when the script was compiled but is absent or differently declared in the executor that loads it.
  • The category does not identify which plugin or unit should provide the symbol. Preserve the name/declaration and the Velox/product version when diagnosing it.
  • Do not catch this error and continue using the same partially loaded script. Correct the configuration or recompile against the current Code Library.
  • Exception transfer is not a database, dataset, filesystem or external-system transaction. Any earlier side effect remains unless the called API or surrounding Flow provides an explicit rollback contract.
  • Do not persist the numeric ordinal as an integration contract. Store the member name, formatted message, parameter and relevant procedure/position with the Velox version.

Related Code Library entries

External references

Created 2026-07-15