Experimental Physics and
Industrial Control System

Andrew Johnson via Core-talk <core-talk at aps.anl.gov> · Mon, 10 Aug 2020 23:10:23 -0000

@Mark This won't prevent applications from parsing octal numbers in
strings, it's just where you're wanting to include a non-ASCII character
in a string field, something like this:

  field(FVST, "F\374nf") # "Fünf" using the ISO-8859-1 char-set

which would have to be spelled like this instead:

  field(FVST, "F\xFCnf")

@Dirk The JSON5 spec is a small subset of the ECMAScript 5.1 language spec, so they're just following what that standard said. Actually the epicsStrnRawFromEscaped() routine will still accept a single hex digit, but the dbLoadRecords() lexer will complain if it doesn't see two.

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

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System