JSON also requires UTF-8 (which is not really supported anywhere else in
EPICS, AFAIK). Thus using non-ASCII Latin-1 chars would be illegal. But
it does not complain about Latin-1 encoded äöü which may have their
place in DESC for example, or μ and ° in EGU.
--
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/1940283
Title:
Misleading Error: Invalid character '"'
Status in EPICS Base:
New
Bug description:
When using a tab character in a field, EPICS 7 prints a misleading
error message, not hinting at the tab but at the closing(?) quote.
Example 1: field(DESC, "a b")
Example 2: info(TAB, "a b")
Error: Invalid character '"'
at or before """ in path "." file "..." line ...
BTW: Is there a reason why I cannot use a tab in my (info) fields?
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1940283/+subscriptions
- References:
- [Bug 1940283] [NEW] Misleading Error: Invalid character '"' Dirk Zimoch via Core-talk
- Navigate by Date:
- Prev:
[Bug 1940283] Re: Misleading Error: Invalid character '"' Andrew Johnson via Core-talk
- Next:
[Bug 1940283] Re: Misleading Error: Invalid character '"' Dirk Zimoch 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 1940283] Re: Misleading Error: Invalid character '"' Andrew Johnson via Core-talk
- Next:
[Bug 1940283] Re: Misleading Error: Invalid character '"' Dirk Zimoch 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
|