> It's unfortunate that your reader/write is of course
> similar to std::string, MFC::CStr, ... and yet
> we can't use any of the existing but have to make
> our own again, but I guess that's just the way it is.
>
Both StringEditor and StringSegment are only interfaces. String accessor
objects conforming to these interfaces can be created for std::string,
MFC::CStr, ...
And if we need a fast non-contiguous string we can do that too within a
bounded effort as long as we don't try to fully reproduce every useful thing
that can ever be done with strings.
> C++ just doesn't live up to any of the sharing-of-code dreams.
Actually C++ appears to be serving its purpose just fine in this situation
allowing us to leverage off of std::string when we need bells and whistles
and also use a faster string in the IOC when we care about efficiency - both
through a common interface.
Jeff
- References:
- Re: data access structures, strings Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
RE: data access structures, strings Jeff Hill
- Next:
Re: data access structures, strings Andrew Johnson
- Index:
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: data access structures, strings Kay-Uwe Kasemir
- Next:
Re: data access structures, strings Andrew Johnson
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|