\x should definitely limit itself to 2 hex digits.
Is is worth the effort to pre-process the strings and translate e.g.
\033 to \x1b and \a to \x07 so the json parser understands it? Problem
is that the string may become longer and thus replacement cannot be done
in-place.
--
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
- Navigate by Date:
- Prev:
[Bug 1783475] Re: const link support can't handle escaped charactors Andrew Johnson via Core-talk
- Next:
Build failed: EPICS Base 7 base-R7.0.4.1-rc1-53 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
- Navigate by Thread:
- Prev:
[Bug 1783475] Re: const link support can't handle escaped charactors Andrew Johnson via Core-talk
- Next:
[Bug 1783475] Re: const link support can't handle escaped charactors Andrew Johnson 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
|