On Nov 13, 2012, at 1:02 PM, Mark Rivers <[email protected]> wrote:
> Folks,
>
> I have now tested changing asynPortDriver so that it returns strlen(value)+1 in readOctet and octetCallback.
>
> …..SNIP…...
>
> So it is NOW CORRECT. Because NORD now includes the trailing Nil the version of camonitor in base 3.14.12.2 works OK.
>
> So do we agree with Andrew's recommendation that NORD should including the trailing Nil, or should NORD be the actual number of elements that were read, and clients must be fixed to handle this if they want to use long string support?
>
I vote for the latter.
Drivers, such as ASYN IP port and TTY, set NORD as the number of characters in whatever message they received -- no '+1' for a terminating 0. Clients should abide by this.
Starting down the slippery slope of having NORD sometimes mean 'including the terminator' and sometimes 'just the string' seems like it's going to cause lots of problems and weird inconsistencies in the future.
--
Eric Norum
[email protected]
- References:
- Long string support in CA clients and device support Andrew Johnson
- RE: Long string support in CA clients and device support Mark Rivers
- RE: Long string support in CA clients and device support Mark Rivers
- Navigate by Date:
- Prev:
RE: Long string support in CA clients and device support Mark Rivers
- Next:
Re: Long string support in CA clients and device support 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:
RE: Long string support in CA clients and device support Mark Rivers
- Next:
Re: Long string support in CA clients and device support 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·