Thanks Andrew for looking at this.
I understand the situation. I'm not going to work on a patch for this.
I'd rather move to something that creates the iocsh-scripts for me from a template, like jinja2.
--
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/1932153
Title:
iocsh ignores inline-comment
Status in EPICS Base:
Opinion
Bug description:
A function call in iocsh, followed by a comment does not work as
expected.
observed behaviour:
```
epicsEnvSet("VAR", "0") # set VAR to a very important value. For VAR>42 blah blah
```
is creating an empty file named `42` in $PWD.
expected behaviour:
All characters after the '#' character should be treated as comment.
test versions:
3.14.12 and 7.0.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1932153/+subscriptions
- References:
- [Bug 1932153] [NEW] iocsh ignores inline-comment Niko Kivel via Core-talk
- Navigate by Date:
- Prev:
[Bug 1932120] Re: callbackRequest potentially accesses uninitialized memory Dirk Zimoch via Core-talk
- Next:
[Bug 1932118] Re: Bug in vxWorks epicsAtomicCmpAndSwapIntT mdavidsaver 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 1932153] Re: iocsh ignores inline-comment Andrew Johnson via Core-talk
- Next:
Build failed: epics-base base-rtems5-dhcp-710 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
|