diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html index ec45380..a575a95 100644 --- a/documentation/RELEASE_NOTES.html +++ b/documentation/RELEASE_NOTES.html @@ -3,6 +3,7 @@
This is replaced by std::string.
+In timeStamp nanoSeconds is changed to nanoseconds.
+In valueAlarm hystersis is changed to hysteresis
pvData.h and pvIntrospect no longer defines toString Instead they have stream support. diff --git a/documentation/RELEASE_NOTES.md b/documentation/RELEASE_NOTES.md index 8c03979..06c7841 100644 --- a/documentation/RELEASE_NOTES.md +++ b/documentation/RELEASE_NOTES.md @@ -5,6 +5,7 @@ The main changes since release 3.0.2 are: * array semantics now enforce Copy On Write. * String no longer defined. +* timeStamp and valueAlarm name changes * toString replaced by stream I/O * union is new type. * copy is new. @@ -25,6 +26,14 @@ String no longer defined This is replaced by std::string. +timeStamp and valueAlarm name changes +-------------- + +In timeStamp nanoSeconds is changed to nanoseconds. + +In valueAlarm hystersis is changed to hysteresis + + toString replaced by stream I/O --------- diff --git a/documentation/pvDataCPP.html b/documentation/pvDataCPP.html index bbe60d0..6416981 100644 --- a/documentation/pvDataCPP.html +++ b/documentation/pvDataCPP.html @@ -199,7 +199,7 @@ It uses only createField. fields.reserve(n); names.push_back("secondsPastEpoch"); fields.push_back(fieldCreate->createScalar(pvLong)); - names.push_back("nanoSeconds"); + names.push_back("nanoseconds"); fields.push_back(fieldCreate->createScalar(pvInt)); names.push_back("userTag"); fields.push_back(fieldCreate->createScalar(pvInt)); @@ -225,7 +225,7 @@ It uses only createField. addNestedStructure("timeStamp")-> setId("time_t")-> add("secondsPastEpoch", pvLong)-> - add("nanoSeconds", pvInt)-> + add("nanoseconds", pvInt)-> add("userTag", pvInt)-> endNested()-> createStructure(); @@ -264,7 +264,7 @@ uri:ev4:nt/2012/pwd:NTScalarArray string message time_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag
An easy way to create a structure with a string array value field and an alarm and time stamp is @@ -284,7 +284,7 @@ uri:ev4:nt/2012/pwd:NTScalarArray string message time_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag 0x607188 @@ -309,7 +309,7 @@ A hard way to create an structure with an enumerated value field and a time stam addNestedStructure("timeStamp")-> setId("time_t")-> add("secondsPastEpoch", pvLong)-> - add("nanoSeconds", pvInt)-> + add("nanoseconds", pvInt)-> add("userTag", pvInt)-> endNested()-> createStructure(); @@ -323,7 +323,7 @@ uri:ev4:nt/2012/pwd/NTEnum string[] choices time_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag
The following is an easy way. Note that it has two additional @@ -344,7 +344,7 @@ uri:ev4:nt/2012/pwd:NTEnum string message time_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag @@ -370,7 +370,7 @@ union int intValue time_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag structure with value field being a union @@ -380,7 +380,7 @@ uri:ev4:nt/2012/pwd:NTUnion int intValue time_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag alarm_t alarm int severity @@ -388,7 +388,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag @@ -436,7 +436,7 @@ structure string message time_t timestamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag structure power double value @@ -480,7 +480,7 @@ uri:ev4:nt/2012/pwd:NTScalar string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x607268 from get 100000 @@ -513,7 +513,7 @@ uri:ev4:nt/2012/pwd:NTScalarArray string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x607268 via getData 0 1 2 3 4 5 6 7 8 9 @@ -536,7 +536,7 @@ uri:ev4:nt/2012/pwd:NTEnum string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x607268 @@ -571,7 +571,7 @@ structure string message time_t timestamp_t long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 structure power double value 0 @@ -616,7 +616,7 @@ uri:ev4:nt/2012/pwd:NTUnion union value time_t long secondsPastEpoch 1000 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 alarm_t alarm int severity 0 @@ -624,7 +624,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x60a2c8 uri:ev4:nt/2012/pwd:NTUnion @@ -636,7 +636,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x60a2c8 @@ -663,7 +663,7 @@ uri:ev4:nt/2012/pwd:NTUnion any value time_t long secondsPastEpoch 1000 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 alarm_t alarm int severity 0 @@ -671,7 +671,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x60a2c8 uri:ev4:nt/2012/pwd:NTUnion @@ -683,7 +683,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x60a2c8 @@ -766,7 +766,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag 0x60a2c8 data @@ -779,7 +779,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x60a2c8 select valueDouble @@ -792,7 +792,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x60a2c8 value = 1.55 @@ -808,7 +808,7 @@ uri:ev4:nt/2012/pwd:NTUnion string message time_t timeStamp long secondsPastEpoch 0 - int nanoSeconds 0 + int nanoseconds 0 int userTag 0 0x60a2c8 value = 1.65 @@ -1569,7 +1569,7 @@ StructureConstPtr example = standardField->scalar( string message timeStamp_t timeStamp long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag
In addition there are methods that create each of the property structures, @@ -2797,7 +2797,7 @@ value field has properties alarm, timeStamp, and display.
string message timeStamp_t long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag display_t double limitLow 0.0 @@ -2823,7 +2823,7 @@ structure powerSupplySimple string message timeStamp_t long secondsPastEpoch - int nanoSeconds + int nanoseconds int userTag powerSupplyValue_t voltage double value @@ -2943,17 +2943,17 @@ stack. For example the following is permitted:A timeStamp is represented by the following structure
structure timeStamp
long secondsPastEpoch
- int nanoSeconds
+ int nanoseconds
int userTag
The Epoch is the posix epoch, i.e. Jan 1, 1970 00:00:00 UTC. Both the -seconds and nanoSeconds are signed integers and thus can be negative. Since the +seconds and nanoseconds are signed integers and thus can be negative. Since the seconds is kept as a 64 bit integer, it allows for a time much greater than the -present age of the universe. Since the nanoSeconds portion is kept as a 32 bit +present age of the universe. Since the nanoseconds portion is kept as a 32 bit integer it is subject to overflow if a value that corresponds to a value that is greater than a little more than 2 seconds of less that about -2 seconds. The support code always adjust seconds so that the nanoSecconds part is normlized, -i. e. it has is 0<=nanoSeconds<nanoSecPerSec..
+i. e. it has is 0<=nanoseconds<nanoSecPerSec..Two header files are provided for manipulating time stamps:
where