[Bug 1935037] Re: Invalid charactor in field name

[mdavidsaver via Core-talk <core-talk at aps.anl.gov>]

Also, I've taken advantage of this restriction with PVXS to allow an
extended syntax for traversing into structures, unions, and arrays.  eg.

> pvxs::Value top;
> top["value[5]->ufld1"] = ...

This takes a 'top' Structure, traverses to the 'value' field, which is
an array of Unions.  Then indexing the 5th element, and then
accessing/selecting the 'ufld1' member of the Union.

Right now my parsing doesn't handle a Structure field named "in-valid",
although it could (no following '>').

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1935037

Title:
  Invalid charactor in field name

Status in EPICS Base:
  New

Bug description:
  When creating a group in QSRV, the allowed characters are too
  restrictive

  error:
  Error Group not created: Invalid charactor '-' (45) in field name "BI02-TimeRise" must be A-Z, a-z, 0-9, or '_'

  expected behaviour:
  pva structures should allow for a more liberal set of characters that just what is covered by \w regex metacharacter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1935037/+subscriptions