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 <2020> 2021 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 <2020> 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: weird record names? |
From: | Jack via Tech-talk <tech-talk at aps.anl.gov> |
To: | Michael Davidsaver <mdavidsaver at gmail.com>, EPICS Tech-Talk <tech-talk at aps.anl.gov> |
Date: | Tue, 9 Jun 2020 08:27:27 +0200 |
Hi Michael,
the naming convention of SPES project contain the characters: ^ _
Thanks,
-Mauro
I'm looking to collect examples of epics record names in the wild. This is an early step towards (maybe) adding restrictions on what characters a record name can contain, and in what positions. eg. restricting possible first and last characters. In particular I'm looking for examples including characters beyond the usual alphanumeric separated by ':' or '-'. And in what positions they may (or may not) appear. An example from the NSLS2 naming convention (for which I am have some responsibility).TST{evm:1D-DlyGen:31}Evt:Trig2-SPWhich is notable for containing "{" and "}" in the middle. As background. At present, records can be created with almost any characters in a name.record(ai, "a b") {} record(ai, "x.y") {} record(ai, "x\"") {}However, record names including '.' can't be addressed and aren't very useful. Further, names including spaces can't be targeted by links. On the subject of links. Dirk was surprised to find that the syntax for link parsing treats "[0]" as a record name, but "[0,1]" as a constant array. https://bugs.launchpad.net/epics-base/+bug/1882520 Rather than carving out another exception, I'd like to look at coding a general rule.
Mauro Giacchini
Control
System Specialist ISTITUTO NAZIONALE DI FISICA
NUCLEARE
p/f: 0039.049.80.68.558 a: Viale universita' 2, 35020
Legnaro, PD -ITALY-
e: mauro.giacchini at lnl.infn.it s: yakman000
|