Re: weird record names?

[Jiro Fujita via Tech-talk <tech-talk@aps.anl.gov>]

Not for production, but I have tried with Japanese characters once.  It sort of work.  At least I was able to use caget/caput/camonitor.  Did not work with MEDM at all (no surprise).  I sort of worked fine with CSS BOY screen, if I recall.  But I tried only with my Mac.  I didn’t bother trying the same record works from Linux nor Windows.  I can try again, if you want me to.  

Jiro

> On 2020 06 09, at 17:00, Michael Davidsaver via Tech-talk <tech-talk@aps.anl.gov> wrote:
> 
> On 6/8/20 11:35 PM, Maren Purves wrote:
>> We  have underscores as well. I consider those normal.
> 
> 
> My purpose is to catalog what is actually being used, and not to pass
> judgement on "normal".  My putting "weird" in the subject line was
> shameless click bait to hopefully gather more data.
> 
> Any unicode record names out there?
> 
> 
>> Maren Purves
>> East Asian Observatory/JCMT
>> 
>> On Mon, Jun 8, 2020 at 8:27 PM Jack via Tech-talk <tech-talk@aps.anl.gov <mailto:tech-talk@aps.anl.gov>> wrote:
>> 
>>    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-SP
>>>    Which 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@lnl.infn.it <mailto:mauro.giacchini@lnl.infn.it> s: yakman000 
>>     
>> 
>>     
>> 
>> 
>>    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>    Avast logo <https://www.avast.com/antivirus> 	
>> 
>>    Questa e-mail è stata controllata per individuare virus con Avast antivirus.
>>    www.avast.com <https://www.avast.com/antivirus>
>> 
>> 
>>    <#m_-6962127449305410035_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> 
>