Hi Iian,
I think we need to know quite a bit more about what you're trying to do, and where/when these configuration files will be read and/or written. The answers are likely to be very different depending on what you tell us, and I don't think anyone wants to spend time answering the wrong question.
- Andrew
--
Sent from my iPad
> On Oct 6, 2017, at 6:22 PM, Iain Marcuson <[email protected]> wrote:
>
> I need to create support for reading and writing a configuration file, but I also have to support non-EPICS environments. I am thus considering making a library to be used in the IOC. My present idea is to pass EPICS a pointer to a structure containing all the configuration options. However, I do not know what best practices are for mapping PVs to the memory location. What are the accepted methods?
>
> Thank you,
>
> Iain.
>
>
- Replies:
- RE: Writing PVs from an amalgamated structure Iain Marcuson
- References:
- Writing PVs from an amalgamated structure Iain Marcuson
- Navigate by Date:
- Prev:
Re: Asyn GPIB proto file exception @writetimeout Mark Rivers
- Next:
Opportunities at Australian Synchrotron Paul Martin
- 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:
Writing PVs from an amalgamated structure Iain Marcuson
- Next:
RE: Writing PVs from an amalgamated structure Iain Marcuson
- 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
|