Re: Possible to create aliases for record fields?

["Hu, Yong via Tech-talk" <tech-talk at aps.anl.gov>]

Michael, we are talking about fields here. So “det1:NELM.RTYP” itself is not valid.

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>
Date: Monday, January 2, 2023 at 3:37 PM
To: Zimoch Dirk <dirk.zimoch at psi.ch>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Possible to create aliases for record fields?

On 12/28/22 03:47, Zimoch Dirk via Tech-talk wrote:
> At the moment, that is not possible. I had planned for quite some time to implement that.

> ... But I don‘t know what the core developers think of this.

Aliasing fields seem like a reasonable feature.  Although it isn't yet clear
to me how this would work in detail.  eg. to take an example from below.

>> alias("det1.NELM", "det1:NELM")

What would "caget det1:NELM.RTYP" return?

There may also be complications depending on what changes to the
'struct dbBase' tree would be needed.



> Dirk
>
>> Am 20.12.2022 um 19:50 schrieb Li, Ji via Tech-talk <tech-talk at aps.anl.gov>:
>>
>> 
>> Hi,
>>
>> I'm trying to access record fields as PVs using alias command, such as:
>>
>> alias("det1.NELM", "det1:NELM")
>> alias("det1.TSEN", "det1:TSEN")
>>
>> The IOC didn't report errors, but apparently they all pointed to det1 as the change to det1 appeared on these aliases, and vice versa, and this was proved by dbla.
>>
>> If alias command is not the right choice, are there any ways to create aliases/dummy PVs for fields?
>>
>> Best,
>> -Ji Li
>>