Linked by Eugenia Loli-Queru on Mon 5th Dec 2005 05:39 UTC
Strings - such as command-line arguments, environment variables, and console input - are of special concern in secure programming because they comprise most of the data exchanged between an end user and a software system. This chapter covers the security issues with strings and how you can sidestep them.
Thread beginning with comment 68872
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-07
PS: When an article uses "C" and "C++" as if they were the same language, then you know the article does not hold a very deep knowledge of C++.
Exactly!
My guess is that mentioning C++ is required marketing wise.
You write a book about proper C coding but to get better sales your title has to include C++ as well.
Maybe for those "C++" programmers that are misusing C++ as C with classes.
I mean, streaming from cin into a fixed length char buffer? come on
Who does that in other languages that have string classes and then complains about getting an out of bounds exception?
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
Just use std::string like all C++ textbooks recommend. When bound to use C char array, use std::string.c_str() function. What can be easier?
Agreed.
The author is making a lot of noise around a non-issue; at least in C++.
PS: When an article uses "C" and "C++" as if they were the same language, then you know the article does not hold a very deep knowledge of C++.