Experimental Physics and
| |||||||||||||||
|
I don't know. I would expect the user tag to come from a different source than the wall clock time, and be assembled into the NT timeStamp structure. In the NT discussion we expected 32 bits to be good enough for a user tag. More than four billion different values for a tag seem plenty. In general, the NT types were discussed, reviewed and set over years. I would not expect to see them changed on an ad-hoc basis. Not saying that this specific tag should not be 64 bits wide, but to change an existing approved design, I would like to see a minimum amount of justification and discussion. Cheers, ~Ralph On Mon, Oct 9, 2017 at 2:23 PM, Johnson, Andrew N. <[email protected]> wrote: I just tried modifying the definition of the epicsTimeStamp object, adding an epicsUInt64 userTag member to it. Everything built without problems and the tests all passed. Then I looked through pvDataCPP and connected this to the userTag in property/timeStamp.cpp.
| ||||||||||||||
ANJ, 21 Dec 2017 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |