Hi Mark,
You are right: these records have been introduced in 3.15 about 3 years ago (merged in October 2013, released as part of 3.15.0.2 a year later); the appropriate release note entry is missing. Must have been slipped, sorry for that.
I think I remember them being covered in status talks at Collaboration Meetings, though.
The wikified Record Reference Manual is explicitly covering the 3.14 release series, in which these records do not exist.
They are on the to-do list for the new, embedded record type documentation (check the *.dbd.pod files in the source tree), but have not been covered yet.
@all: the Collaboration Meeting next week will be your chance to talk about how to contribute to EPICS Base. Documentation is a nice field of opportunities.
Cheers,
~Ralph
Hi Ralph,
When were the lsi and lso records introduced? They do not seem to exist in 3.14.12.6. I have searched the latest release notes for 3.14, 3.15, 3.16, and 7.0, and the first mention I see is in this:
**********************************************
Changes made between 3.15.3 and 3.15.4
New string input device support "getenv"
A new "getenv" device support for both the stringin and lsi (long string input) record types can be used to read the value of an environment variable from the IOC at runtime. See base/db/softIocExit.db for sample usage.
**********************************************
Note that this does not introduce the records, it just describes a new device support, and it only mentions the lsi record, not the lso.
The records are not documented in the record reference manual here:
https://wiki-ext.aps.anl.gov/epics/index.php/RRM_3-14
The git log indicates that the lsi record was added in 2012.
***************************
commit e01a428059d1c2217ec73660503c0ae81be0aa7b
Author: Andrew Johnson <[email protected]>
Date: Thu Nov 29 13:45:13 2012 -0600
Added new Long String Input record type "lsi"
With Soft Channel device support.
***************************
Since I was not aware that these records had been introduced I don't think they can be used with standard asyn device support?
Thanks,
Mark
