Experimental Physics and
Industrial Control System

Hi, In the "Guidelines and rules for plugins" is this statement: "Obviously [plugins] must not access memory locations that other threads could modify [while the mutex lock is not taken], so they should only access local variables, not class variables (which includes the parameter library)". I think it should be OK to access member variables of the plugin class (i.e. the class derived from NDPluginDriver), in addition to local (stack) variables.  And I presume that by "class variables" what's meant is members that are generally referred to in C++ as static member variables.  Am I correct? Cheers, Phil -- Pixel Analytics is a limited company registered in England. Company number: 7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP

Replies:

RE: areaDetector plugins: what variables can be accessed while unlocked? Mark Rivers

Navigate by Date:

Prev: RE: ai RVAL via asyn + modbus: getting unsigned integer jon

Next: RE: areaDetector plugins: what variables can be accessed while unlocked? Mark Rivers

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 

Navigate by Thread:

Prev: RE: areaDetector: plugin in separate dll Mark Rivers

Next: RE: areaDetector plugins: what variables can be accessed while unlocked? Mark Rivers

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