EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Fw: Multiline statement in iocsh
From: Mark Rivers via Tech-talk <[email protected]>
To: tech-talk <[email protected]>
Date: Thu, 16 Jan 2020 02:48:45 +0000
Forgot to include tech-talk on this message this morning.


________________________________
From: Mark Rivers
Sent: Wednesday, January 15, 2020 10:47 AM
To: 'Konrad, Martin'; Saeed Haghtalab; Ralph Lange
Subject: RE: Multiline statement in iocsh

In areaDetector we try to improve readability using environment variables and comments:

# The port name for the detector
epicsEnvSet("PORT",   "SIM1")
# The maximum image width; used to set the maximum size for this driver and for row profiles in the NDPluginStats plugin
epicsEnvSet("XSIZE",  "1024")
# The maximum image height; used to set the maximum size for this driver and for column profiles in the NDPluginStats plugin
epicsEnvSet("YSIZE",  "1024")

# Create a simDetector driver
# simDetectorConfig(const char *portName, int maxSizeX, int maxSizeY, int dataType,
#                                   int maxMemory, int priority, int stackSize)
simDetectorConfig("$(PORT)", $(XSIZE), $(YSIZE), 1, 0, 0,0)

Mark


-----Original Message-----
From: Tech-talk <[email protected]> On Behalf Of Konrad, Martin via Tech-talk
Sent: Wednesday, January 15, 2020 9:41 AM
To: Saeed Haghtalab <[email protected]>; Ralph Lange <[email protected]>; EPICS Tech Talk <[email protected]>
Subject: Re: Multiline statement in iocsh

Hi,
On 1/15/20 10:31 AM, Saeed Haghtalab via Tech-talk wrote:
> That's right. I've put the comments in each line deliberately because
> I think since startup script mostly contains the commands and
> configuration (and not code) with many arguments and macro
> substitution, I think it makes sense to support inline comment in
> multiline statement in this case which helps in readability a lot.
In my experience comments tend to be wrong after a while. To me it sounds like we actually want support for named arguments [1].

-Martin

[1] https://en.wikipedia.org/wiki/Named_parameter

--
Martin Konrad
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: [email protected]

References:
Multiline statement in iocsh Saeed Haghtalab via Tech-talk
Re: Multiline statement in iocsh Ralph Lange via Tech-talk
Re: Multiline statement in iocsh Konrad, Martin via Tech-talk

Navigate by Date:
Prev: RE: EtherIP EPICS Support: Invalid Service 0x52 Guerra, Roy Ignacio via Tech-talk
Next: Re: EtherIP EPICS Support: Invalid Service 0x52 Kasemir, Kay via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Multiline statement in iocsh Johnson, Andrew N. via Tech-talk
Next: Question about two minor issues with IOCs Wlodek, Jakub via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
ANJ, 16 Jan 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·