1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 <2024> 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 <2024> 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: dbGetField AI.DPVT |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Dave Bracey <dbracey at fnal.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 22 Jul 2024 20:48:32 +0000 |
Hi Dave, There's a reason the DPVT field is called "Device Private" — it's not intended to be accessible from outside the device support code which owns it. Think of it like a C++
private: class-member access specifier. That doesn't mean it's impossible for other software running inside the IOC to get to it, but dbGetField() can't do it by design. What's the higher-level problem that you're trying to solve which seems to require this? Please describe that to the list and we can try to offer other approaches that wouldn't require you to break the encapsulation. - Andrew |