Talk About Network



Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Programming > C++ Moderated > pitfalls of str...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 4 Topic 9529 of 9593
Post > Topic >>

pitfalls of string for binary data

by Brendan <catphive@[EMAIL PROTECTED] > Apr 22, 2008 at 11:43 AM

At a prior job, people were using std::string to hold arbitrary binary
data, as opposed to vector<char>. I've seen a few people in this group
poopoo that notion, and I'd like to find out what they think the
pitfalls, if any, of using string to hold binary data are. I ask,
because otherwise the code base was pretty high quality, and string
does offer a number of extra search based member functions that vector
does not.

Additionally, is there any strong reason to use unsigned char as
opposed to char to hold binary data where the high order bit might be
set? Again, in practice I've mostly seen char used.

Thanks

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]




 4 Posts in Topic:
pitfalls of string for binary data
Brendan <catphive@[EMA  2008-04-22 11:43:17 
Re: pitfalls of string for binary data
Lance Diduck <lancedid  2008-04-22 15:19:17 
Re: pitfalls of string for binary data
"Charles" <e  2008-04-22 22:27:13 
Re: pitfalls of string for binary data
Marco Manfredini <ok_n  2008-04-23 14:13:18 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Wed May 14 19:20:09 CDT 2008.