I'm wondering if there's a difference in using size_t and container::size_type? What I understand is size_t is more generic and can be used for any size_types.. Is container::size_type more optimized for a specific container though? ...
Why is it that in C++ containers, it returns a size_type rather than an int? If we're creating our own structures, should we also be encouraged to use size_type? ...
const std::string::size_type cols = greeting.size() + pad * 2 + 2; Why string::size_type? int is supposed to work! it holds numbers!!! ...
If you go in my post history you'll see that i'm trying to develop an interpreter for a language that i'm working on. I want to use *size_t* using two different codes, but they all return nothing. Here is the post of what i was trying: http://stackoverflow.com/questions/1215688/read-something-after-a-word-in-c When i try to use the ...
I often have classes that are mostly just wrappers around some STL container, like this: class Foo { public: typedef std::vector<whatever> Vec; typedef Vec::size_type size_type; const Vec& GetVec() { return vec_; } size_type size() { return vec_.size() } private: Vec vec_; }; I am not so sure about returning size_type. Often...