2002 2003 2004 <2005> 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 <2005> 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: ICE and TIPC |
From: | Andrew Johnson <[email protected]> |
To: | Kay-Uwe Kasemir <[email protected]> |
Cc: | EPICS Core Talk <[email protected]> |
Date: | Wed, 27 Jul 2005 12:49:49 -0500 |
Kay-Uwe Kasemir wrote:
Strings are the very data type where I think the end user has to seea contiguous string. In C/C++, the (const char *) is the only common denominatorbetween string classes, all of which of course based on divine revelation but incompatible except for c_str()/CStr()/...
As long as the string API acts like it stores a contiguous string, and provides a method that can copy the string data out into a contiguous external buffer (and add the trailing '\0' as well that the C functions need), you shouldn't notice the difference.
Remember my point about the CA Get request from last night - your callback routine is presented with a property catalog that contains the data you requested from the server. You are responsible for browsing or traversing that catalog and extracting the data from it into your own storage. If a property you're given is a string, you have to copy it to your own buffer anyway. Why do you care how the
value.getCstr(mybuffer, maxlen)method (or whatever we call it) works internally to copy that data into your buffer?
- Andrew -- Podiabombastic: The tendency to shoot oneself in the foot.