Experimental Physics and
Industrial Control System

On 9/5/19 1:35 AM, Ralph Lange via Core-talk wrote:
> I have run into this before.
> I my case, I was lucky and got by with not including EPICS callback.h in a source file where it was not really needed.

In this case callback.h is needlessly included by dbNotify.h,
which must be included by pdbsingle.cpp.

> For EPICS, putting a symbol with a name as generic as "CALLBACK" into the global namespace is pretty much calling for clashes.

Yup.  Last year I started down the road to finally fixing this.

https://github.com/epics-base/epics-base/commit/00a974ce528277de9a95987cfda538ff18e38d8c

Rather than beating my head against this error, I'm more inclined to
take the next step in addressing the root cause by replacing internal
usage of 'CALLBACK' with 'epicsCallback'.  Then adding something like:

> #ifndef EPICS_NO_CALLBACK
> typedef epicsCallback CALLBACK;
> #endif


Of course this doesn't help with previous releases, where Windows will
become unsupported by the pva2pva module until/unless someone can help
to straighten out the include ordering.

Attachment: signature.asc
Description: OpenPGP digital signature

References:

CALLBACK clash Michael Davidsaver via Core-talk

Re: CALLBACK clash Ralph Lange via Core-talk

Navigate by Date:

Prev: Jenkins build is back to normal : epics-base-3.15-win32s-test #236 APS Jenkins via Core-talk

Next: Re: CALLBACK clash Michael Davidsaver via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: CALLBACK clash Ralph Lange via Core-talk

Next: Re: CALLBACK clash Johnson, Andrew N. via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024