| 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: Record/Channel names |
| From: | Andrew Johnson <[email protected]> |
| To: | "Rarback, Harvey" <[email protected]> |
| Cc: | EPICS tech-talk <[email protected]>, "Tony Cox (E-mail)" <[email protected]>, "Wermelskirchen, Clemens" <[email protected]> |
| Date: | Mon, 19 Feb 2001 17:53:59 -0600 |
"Rarback, Harvey" wrote: > > [...] > > CA has no restriction on channel names. Does anybody currently use > > parentheses '()' in non-IOC channel names that are provided using the > > PCAS? > > We do at SPEAR. Tony Cox wrote a CA server that runs on VMS and serves > our ancient control system software constructs with names like > spr:zb/xx7(25).VAL. Ok, thanks for responding. Your example contains non-alphanumeric characters ':/' to the left of the first parenthesis. Will that pattern be true for all such channel names? My original proposal restricted link type names to alphanumerics only, so I can easily use the presence of a non-al/num character before the open parenthesis to flag that this must be an old-style PV name. - Andrew -- Every great idea appears crazy to start with.