A colleague just presented me with one of those frustrating little problems where his database wouldn’t load because he spelled a calcout.OOPT field value using “to” instead of “To” and he couldn’t find it.
How about when putting to a menu field we do a second pass through the choice strings using epicsStrCaseCmp() so this kind of thing would be silently accepted? The first pass should still use
strcmp() in case some IOC has choices (in mbbo strings) that only differ by case, but the second pass would accept the first to match even when the cases differ.
We could make this configurable so sites could turn it off, or even have it display a warning, but I’m not sure who would really want that much strictness.
I already wrote the code, although it could be posted as a Codeathon project instead (requiring tests and Release Notes as well).
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|