[Bug 1783475] Re: const link support can't handle escaped charactors

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

> The same for octal. Who would volutarily use octal?

Many Modbus vendors specify the register addresses in octal, so it can be very convenient to use octal addresses in the link fields for the EPICS modbus driver. For exmaple, search for "octal" in this document.
https://epics-modbus.readthedocs.io/en/latest/

These octal values would occur in the INP and OUT fields of records. I
don't know if those would be impacted by this change?

-- 
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/1783475

Title:
  const link support can't handle escaped charactors

Status in EPICS Base:
  Triaged
Status in EPICS Base 3.16 series:
  Won't Fix
Status in EPICS Base 7.0 series:
  Triaged

Bug description:
  I think the following should work, but it doesn't.  The culprit seems
  to be the call to dbTranslateEscape() in dbRecordField() and
  dbRecordInfo().  The escaped newline is handled correctly by dbLex,
  but the later dbJLinkParse() errors on the now unescaped newline.

  > record(stringin, "test") {
  >      field(INP, {const:"multi\nline"})
  > }

  > dbJLinkInit: lexical error: invalid character inside string.
  >                          {"const":"multi line"}
  >                      (right here) ------^

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