Experimental Physics and
| |||||||||||||||||
|
Hi Michael, the naming convention of SPES project contain the characters: ^ _
Thanks, -Mauro On 08/06/2020 23:08, Michael Davidsaver
via Tech-talk wrote:
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. --
| ||||||||||||||||
ANJ, 09 Jun 2020 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |