On Thu, 4 Feb 2021 at 17:31, Johnson, Andrew N. <
anj at anl.gov> wrote:
On Feb 4, 2021, at 3:29 AM, Ralph Lange via Core-talk <
core-talk at aps.anl.gov> wrote:
In the good old times,
we used to have a static DB parser that was used to provide a "lint" tool for databases. (My mourning of the loss of that feature was largely ignored.)
That program used dbStaticHost, the alternative version which stored all record field values as strings. Support for that was removed in 2012, apparently by me, but it was sufficiently clunky and confusing that I doubt if it could have lasted much longer
anyway.
Didn't mean to say I was fond of that specific piece of code.
I was missing the functionality, but now ... sniff ... I'm over it.
We should provide linting service on the EPICS web page. Would generate nice data of what EPICS features people are using. (And their most common errors.)
"Fixing" bugs on the fly? Rather not. Large blocks of explanations and suggestions on the IOC console? Rather not.
I assume you are against my original suggestion then, since that would be fixing bugs on the fly.
Correct.
Better error messages are always ... better.
But I would avoid lengthy things like listing all available options. That is more useful in an autocomplete pop-up of the editor, not in an IOC log file.
Cheers,
~Ralph
