Re: IOC, QServ, and AMSG / alarm.message

["Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>]

 

On 2/17/25, 12:16 PM, "Michael Davidsaver" <mdavidsaver at gmail.com> wrote:

 

I find myself asking, how should this typo have been detected?

So far, for reasons of forward compatibility, warnings about unknown keys are not

printed by default.  Using the "debug" link support will turn them on.

>    field(INP,{debug:{pva:{pv:"$(P):$(R):CALC", serv: "MS", proc:"CP"}}})

Prints:

> pva link parsing unknown string depth=1 key="serv" value="MS"

> pvaLink pvaOpenLink fails P:R:SIMULATED: DBLINK* corrupt

> iocRun: All initialization complete

At least right now, this does not strike me as a satisfactory answer.

The debug link support plugin was intended more for developers of link support types than for users. It’s a bit too clunky for regular use, but handy to have when debugging the link code. A link type should register a global variable if it wants to allow messages about unknown keys to be suppressed, printed as warnings, or made into errors that abort loading, using the iocsh var command to set it. I would default it to warning.

 

- Andrew

 

-- 

Complexity comes for free, Simplicity you have to work for.