Experimental Physics and
| |||||||||||||||||
|
Thank you Mark & Andrew. Actually, I have also gone through the headers and could not find dbGetLinkValue() and then I tried to incorporate dbGetLink() into the code, however the compilation is done but something is still missing which generates segementation fault. Let me look into it and thank you once again. Regards Anindya VECC , India. -----"Johnson, Andrew N." <anj at anl.gov> wrote: ----- To: "Rivers, Mark L." <rivers at cars.uchicago.edu> From: "Johnson, Andrew N." <anj at anl.gov> Date: 03/19/2020 09:47PM Cc: "Anindya Roy" <r_ani at vecc.gov.in>, "EPICS tech-talk" <tech-talk at aps.anl.gov> Subject: Re: error calling dbGetLinkValue in EPICS base-3.15.6 On Mar 19, 2020, at 7:49 AM, Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> wrote:
… which is why we’re trying to move the source of the documentation closer to the code by adopting Doxygen. It will probably take several years to get there though. > Surprisingly to me this change in the API is also not mentioned in the 3.15.* release notes. Mea cupla. There were quite a lot of changes when I was working on adding extensible link types and they didn’t all get documented.
Those have been fixed in the 7.0 tree, probably sometime in 3.16 branch.
Correct. dbGetLink() was a macro that only actually called the dbGetLinkValue() routine if there was something for it to do; passing *nRequest==0 allowed you to fetch metadata such as an array length without getting the actual data. Since everyone was supposed to be using dbGetLink() I removed the short-circuit and renamed the routine while cleaning up the code. - Andrew -- Complexity comes for free, simplicity you have to work for.
| ||||||||||||||||
ANJ, 20 Mar 2020 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |