Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
<== Date ==> <== Thread ==>

Subject: Re: EPICS 7.0.2.1 release preparation
From: Dirk Zimoch via Core-talk <core-talk@aps.anl.gov>
To: <core-talk@aps.anl.gov>
Date: Wed, 3 Apr 2019 15:31:40 +0200
Hi,

I have seen that dbGetFieldType() and dbGetLinkType() are about to be removed. What is the replacement for dbGetLinkType()? I want to find out if a field is a PV link.

I use it in a utility function "dbll" (database list links) to show which records link to given records or field: dbll recordpattern[.field]

The core of the function is:

for (status = dbFirstRecordType(&dbEntry); !status; status = dbNextRecordType(&dbEntry)) for (status = dbFirstRecord(&dbEntry); !status; status = dbNextRecord(&dbEntry))
    {
#if EPICS_VERSION*10000+EPICS_REVISION*100+EPICS_MODIFICATION >= 31411
        if (dbIsAlias(&dbEntry)) continue;
#endif
for (status = dbFirstField(&dbEntry, 0); !status; status = dbNextField(&dbEntry, 0))
        {
            if (dbGetLinkType(&dbEntry) == DCT_LINK_PV)
            {
const char* target = ((DBLINK *)dbEntry.pfield)->value.pv_link.pvname;
                if (!match || (
                        (strchr(target, '.') ? 1 : 0) == (d ? 1 : 0) ?
                            epicsStrGlobMatch(target, match) :
alt_match ? epicsStrGlobMatch(target, alt_match) : 0))
                {
printf("%s.%s ==> %s\n", dbGetRecordName(&dbEntry), dbGetFieldName(&dbEntry),
                        dbGetString(&dbEntry));
                }
            }
        }
    }
    dbFinishEntry(&dbEntry);

Dirk

On 14.03.19 03:10, Michael Davidsaver via Core-talk wrote:
All,

We're planning to make a minor release of Base ahead of the core dev. meeting
at SLAC in 2 weeks.  Hopefully early next week.  The intent is to release the
bug fixes which have accumulated since 7.0.2 in December before we merge more
extensive changes during the meeting.

This mail is a call for testers and Base module owners to commit/submit any
fixes already known.

Michael



The outstanding un-merged fixes I'm aware of which may meet this criteria are:

https://bugs.launchpad.net/epics-base/+bug/1812084

https://github.com/epics-base/epics-base/pull/24



The fixes which have been committed should be listed in the module release notes.


https://github.com/epics-base/epics-base/blob/7.0/documentation/RELEASE_NOTES.html

https://github.com/epics-base/pvDataCPP/blob/master/documentation/release_notes.dox

https://github.com/epics-base/pvAccessCPP/blob/master/documentation/release_notes.dox

https://github.com/epics-base/normativeTypesCPP/blob/master/documentation/RELEASE_NOTES.md

https://github.com/epics-base/pva2pva/blob/master/documentation/release_notes.dox

No changes have been made to pvaClient and pvDatabase since 7.0.2


Replies:
Re: EPICS 7.0.2.1 release preparation Johnson, Andrew N. via Core-talk
References:
EPICS 7.0.2.1 release preparation Michael Davidsaver via Core-talk

Navigate by Date:
Prev: Re: How to ensure epicsThread function is running in short-lived environment? Dirk Zimoch via Core-talk
Next: Re: How to ensure epicsThread function is running in short-lived environment? Michael Davidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
Navigate by Thread:
Prev: EPICS 7.0.2.1 release preparation Michael Davidsaver via Core-talk
Next: Re: EPICS 7.0.2.1 release preparation Johnson, Andrew N. via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
ANJ, 03 Apr 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·