Module attr_plot_args 

NDAttrPlotConfig’s positional-argument mapping, kept apart from the command that installs it.

The mapping is the parity-critical half of that command and it is pure: &[ArgValue] in, six fields out, no port manager, no IOC, no reactor. It lives here rather than in crate::ioc because that module is gated on tokio_backend — it stands an IOC up on epics_ca_rs::server::ioc_app, which the reactor-free backend does not have — and a gate sized for the IocApplication type surface took this parsing and its three boundary cases down with it.

The predicate here is not(epics_embedded_target) instead, which is what ArgValue itself is gated on: the iocsh registry is host-and-VxWorks- and-RTEMS-absent, not reactor-dependent, so a host exec_backend build keeps both it and this.

crate::ioc is named in a code span rather than linked for the same reason this module exists: it is not there to link to in the very configuration this paragraph is explaining.

Structs

AttrPlotArgs

Parsed NDAttrPlotConfig arguments.

Functions

parse_attr_plot_args

Parse NDAttrPlotConfig positional args in C order (NDPluginAttrPlot.cpp:308): port, n_attributes, cache_size, n_selected_blocks, in_port, in_addr, queue_size, ....