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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | TPRO Field Definition |
From: | "Dudley, David" <[email protected]> |
To: | "[email protected] Talk" <[email protected]> |
Date: | Fri, 31 Jan 2014 14:27:07 +0000 |
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
![]() |