Am 04.02.21 um 01:21 schrieb Johnson, Andrew N. via Core-talk:
> 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).
A fat +1 from me. And I would include DBF_ENUM, too, if that is feasible.
Cheers
Ben
--
I would rather have questions that cannot be answered, than answers that
cannot be questioned. -- Richard Feynman
Attachment:
signature.asc
Description: OpenPGP digital signature
- References:
- CaSe-IndepeDent Menu SEARches? Johnson, Andrew N. via Core-talk
- Navigate by Date:
- Prev:
Re: CaSe-IndepeDent Menu SEARches? Ralph Lange via Core-talk
- Next:
Re: CaSe-IndepeDent Menu SEARches? Johnson, Andrew N. via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: CaSe-IndepeDent Menu SEARches? Ben Franksen via Core-talk
- Next:
Build failed: epics-base base-menu-suggest-616 AppVeyor via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
|