This document summarizes the changes to the module between releases.
isCompatiblemethods to use a new internal validation API in order to make the implementation uniform, less repetitive and less strict.
The new implementation is less strict in the sense that it considers types that can be converted into one another compatible with each other. For example, any
Scalar is considered compatible with any other
Scalar, regardless of the underlying type. Normative Types users are advised to use
putFrom when getting/putting data from/into
isCompatible methods now disregard field order and extra fields that are not part of the specification.
This change is not expected to break any current server or client, but it will break existing clients that rely on the previous
isCompatible strictness once servers start to take advantage of
isCompatible now being less strict.
This release contains bug fixes and minor source updates needed to build against the latest version of pvData.
The main changes since release 5.1.1 are:
The main changes since release 5.0 are:
Linux shared library version numbers have been added by setting SHRLIB_VERSION (to 5.1 in this case). So shared object will be libnt.so.5.1 instead of libpvData.so.
Source has moved out of nt directory directly into src.
Headers have been moved into a pv directory. This facilitates using some IDEs such as Qt Creator.
src/nt/ntscalar.cpp -> src/ntscalar.cpp src/nt/ntscalar.h -> src/pv/ntscalar.h
is_a(PVStructurePtr const &) implementation has been added for each type.
This release adds support through wrapper classes and builders for the remaining Normative Types:
Release 5.0 therefore implements fully the 16 Mar 2015 version of the normativeTypes specification.
Each wrapper class has an extended API:
Other changes are:
This is the first release of normativeTypesCPP that is part of an official EPICS V4 release. It is a major rewrite of the previous versions of normativeTypesCPP.
This release provides support through wrapper classes and builders for the following Normative Types:
Each type has a wrapper class of the same name which has functions for checking compatibility of existing PVStructures (isCompatible) and the reported types of Structures (is_a), wraps existing PVStructures (wrap, wrapUnsafe) and provides a convenient interface to all required and optional fields.
Each type has a builder which can create a Structure, a PVStructure or a wrapper around a new PVStructure. In each case optional or extra fields can be added and options such as choice of scalar type can be made.
Additional features are: