Experimental Physics and
Industrial Control System

fyi. There is a proposed change to the meaning of the dbRecordsOnceOnly global variable under consideration.
This change would make dbRecordsOnceOnly!=0 less restrictive.

As a reminder, dbRecordsOnceOnly defaults to zero.

https://github.com/epics-base/epics-base/pull/383

Currently with

record(ai, "myrec") {}

dbRecordsOnceOnly!=0 currently disallows appending fields with either form:

record("*", "myrec") {} # error
record(ai, "myrec") {}  # error

This PR changes the meaning such that dbRecordsOnceOnly!=0 always allows appending when explicitly intended (rtype "*").

record("*", "myrec") {} # allowed
record(ai, "myrec") {}  # error

Replies:

Re: Change to dbRecordsOnceOnly? Han Lee via Tech-talk

Navigate by Date:

Prev: Docu/codeathon website Timo Korhonen via Tech-talk

Next: Re: Change to dbRecordsOnceOnly? Han Lee via Tech-talk

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: Docu/codeathon website Timo Korhonen via Tech-talk

Next: Re: Change to dbRecordsOnceOnly? Han Lee via Tech-talk

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