Experimental Physics and
Industrial Control System

woz$ git tip -p

commit a514ab7b51db108336dc234cb774af2603e51696 (HEAD -> master, upstream/master, origin/master, origin/HEAD)

Author: Andrew Johnson <anj at anl.gov>

Date:   Mon Mar 15 12:12:15 2021 -0500

    Add missing removal instructions for destroy()

diff --git a/documentation/RELEASE_NOTES.md b/documentation/RELEASE_NOTES.md

index 6df2527..095b40c 100644

--- a/documentation/RELEASE_NOTES.md

+++ b/documentation/RELEASE_NOTES.md

@@ -5,6 +5,8 @@ This document summarizes the changes to the module between releases.

 ## Release 4.5.3 (EPICS 7.0.5 Feb 2021)

 

 * The previously deprecated destroy methods have been removed.

+  Any application code that was previously calling these can just remove

+  those calls.

 

 ## Release 4.5.2 (EPICS 7.0.3.2 May 2020)

 

On Mar 13, 2021, at 2:52 AM, Ralph Lange via Core-talk <core-talk at aps.anl.gov> wrote:

Thanks, Marty!

On Fri, 12 Mar 2021 at 22:18, Marty Kraimer via Core-talk <core-talk at aps.anl.gov> wrote:
On 3/12/21 8:06 AM, Ralph Lange via Core-talk wrote:

On Fri, 12 Mar 2021 at 12:29, Marty Kraimer via Core-talk <core-talk at aps.anl.gov> wrote:
On 3/12/21 3:41 AM, Ralph Lange via Core-talk wrote:

pvDatabaseCPP:
The destroy() methods have been deprecated in 2019 as part of a commit with the message "fix warning messages; at least on linux".
There seems to be no documentation - neither at the point of deprecation nor at the point of removal - how to migrate applications that are using this method.

I maintain that any application that uses destroy will have problems.
Any application that uses destroy should be fixed.

Yes, Marty, but: how?

If the code is calling the destroy method of base classes just remove the call. 

That sentence should have been in the release notes.

Cheers,
~Ralph