Experimental Physics and
Industrial Control System

Andrew Johnson via Core-talk <core-talk at aps.anl.gov> · Thu, 17 Jun 2021 18:14:39 -0000

Unfortunately inline comments like that have never been supported by iocsh. '#' is just treated as another command which does nothing. Comments are documented in
 https://epics.anl.gov/base/R3-15/6-docs/AppDevGuide/IOCShell.html#x19-74000018.2.5
although that doesn't really clarify that inline comments are not supported.

Given the rather complicated way that iocsh processes each command line
I don't know how easy it would be to actually implement such inline
comments. If you were to work on a patch to implement this, please check
that other commands can still accept # characters inside string
parameters – there may be a fundamental problem there given that
parameters don't have to be enclosed inside quotes, this iocsh command
shows the problem:

epics> echo ###-Hello-###
###-Hello-###

** Changed in: epics-base
   Importance: Undecided => Wishlist

** Changed in: epics-base
       Status: New => Opinion

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

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System