Experimental Physics and Industrial Control System
|
From what I can see TPRO is only ever
tested zero/non-zero.
$ grep -w tpro src/db*/*
src/db/dbAccess.c: unsigned char
tpro=precord->tpro;
src/db/dbAccess.c: if (tpro)
{
src/db/dbAccess.c: if (precord->tpro)
On 01/31/2014 09:27 AM, Dudley, David wrote:
I’m looking through the Documentation on "Fields common to all
record types", and I see that TPRO is defined as:
which seems to imply that the only valid contents are 0 or
1.
I see that TPRO is defined as a UCHAR, in the section
earlier, so I am wondering…..
I need to print varied amounts of information on a record as
it’s being processed, during a debugging session, so can I
plan on using values assigned in TPRO -other- than just 0
and 1 (2,3….) to vary the amount of information printed by
the device driver.
Unless this is a problem, can the definition of that field
be adjusted to state that numbers greater than 0 print
information on the record each time it is processed?
Later-
David Dudley
|
- Replies:
- Re: TPRO Field Definition Andrew Johnson
- References:
- TPRO Field Definition Dudley, David
- Navigate by Date:
- Prev:
TPRO Field Definition Dudley, David
- Next:
Question on How to add a new breakpoint table Goff, Steven J
- 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:
TPRO Field Definition Dudley, David
- Next:
Re: TPRO Field Definition Andrew Johnson
- 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
|
ANJ, 17 Dec 2015 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|