diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html index de85110a5..ca8b63e6c 100644 --- a/documentation/RELEASE_NOTES.html +++ b/documentation/RELEASE_NOTES.html @@ -13,9 +13,43 @@

Changes between 3.14.10 and 3.14.11

+

Added record aliases

+ +

Record definitions can declare their own alias names along with the field +values, or a separate alias statement can also be used:

+ +
record(ai,"canonicalName")
+{
+   alias("firstAlias")
+}
+alias("canonicalName","secondAlias")
+ +

Aliases can only be created for records that have already been loaded by the +IOC, although they don't have to appear in the same .db file. A CA client can +discover that a record name is an alias by fetching its .NAME field, which will +always return the canonical name for the record. Three new routines in the +dbStaticLib library handle aliases:

+ +
long dbCreateAlias(DBENTRY *pdbentry, const char *paliasName);
+int dbIsAlias(DBENTRY *pdbentry);
+long dbDeleteAliases(DBENTRY *pdbentry);
+ +

Aliases are located using the existing record instance API (use +dbIsAlias() to test whether a record is actually an alias or not), and +can be deleted using dbDeleteRecord(). The dbDeleteAliases() +routine exists to delete all aliases of the selected record, and will return an +error if used on an alias.

+ +

Any out-of-tree tools that scan through all the records in the database using +dbFirstRecord() and dbNextRecord() may need modifying to avoid +duplicate processing of aliased record instances. Also note that the set of +info items for a record instance are not shared with its aliases, which each +have their own info item namespace.

+

Added support for RTEMS-mvme2700

-

Supplied by Matt Rippa <mrippa@gemini.edu>. Should work for MVME2400, too.

+

Supplied by Matt Rippa <mrippa@gemini.edu>. Should work for MVME2400, +too.

CA Commandline tools: priority support