On 10/18/2011 11:30 AM, Andrew Johnson wrote:
Hi Michael,
On 2011-10-18 Michael Davidsaver wrote:
I've stumbled onto an interesting behavior of aSub. I want to write a
function which takes a CHAR array as input (a long string). Sometimes
the string can legitimately be empty (length 0). What I find is that
when the the input should go from non-empty to empty it does not, and
instead keeps the previous value.
The number of elements of a long string (char array) must always include the
terminating nil character, thus an empty string must have an element count of
one, not zero. If you don't include the terminator in your element count your
string might get old garbage appended to it.
Ok, so this covers the case of long strings. What about other types
(eg. DOUBLE)? Isn't this an issue of general correctness/proper error
reporting?
Michael
- Replies:
- Re: aSub and zero length arrays Andrew Johnson
- References:
- aSub and zero length arrays Michael Davidsaver
- Re: aSub and zero length arrays Andrew Johnson
- Navigate by Date:
- Prev:
long strings Michael Davidsaver
- Next:
Re: How the EPICS IOC determines the link type {CA_LINK/DB_LINK/CONSTANT} 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
- Navigate by Thread:
- Prev:
long strings Michael Davidsaver
- Next:
Re: aSub and zero length arrays 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
|