Merge ~dirk.zimoch/epics-base:fix_one_element_input_link_arrays into ~epics-core/epics-base/+git/epics-base:7.0

[Dirk Zimoch]

Allow numeric 1 element arrays in constant input links.
Fixes bug #1882520.

Links like
  field (INP, [42])
or
  field (INP, [])
did not work, while
  field (INP, [42,7])
or even
  field (INP, [42,])
were fine.

Instead, they were searching for records with the name "[42]" or "[]", respectively

Now they work as expected.

[Andrew Johnson (anj)]

This change has the potential to break existing EPICS IOC database applications.

review: Disapprove

[Andrew Johnson (anj)]

After further consideration I realize that the breakage I was concerned about does have some reasonable workarounds. An IOC that needs to link to records with names like [something] or even [some]:other:[thing] can still do so by appending a link flag, a field name or even just a dot to the record name in the INP/OUT link value:

  field(INP, "[something] NPP")
  field(INP, "[something].VAL")
  field(INP, "[something].")

My original concern was mainly that such records could never be the target of a link if this change were applied, but that was incorrect.

review: Approve

diff --git a/modules/database/src/ioc/dbStatic/dbStaticLib.c b/modules/database/src/ioc/dbStatic/dbStaticLib.c
index 539ea3a..ceb4ea3 100644
--- a/modules/database/src/ioc/dbStatic/dbStaticLib.c
+++ b/modules/database/src/ioc/dbStatic/dbStaticLib.c
@@ -2330,8 +2330,7 @@ long dbParseLink(const char *str, short ftype, dbLinkInfo *pinfo)
     }
 
     /* Link may be an array constant */
-    if (pstr[0] == '[' && pstr[len-1] == ']' &&
-        (strchr(pstr, ',') || strchr(pstr, '"'))) {
+    if (pstr[0] == '[' && pstr[len-1] == ']') {
         pinfo->ltype = CONSTANT;
         return 0;
     }