standard vector header C++

Hi

Where is the best place to grab an uptodate standard vector header?
LuckyLucksAsked:
Who is Participating?
 
phoffricCommented:
>> But there is no "best policy"/ standard as to where to grab it from ? For example, if i wanted the glew headers, i would go to http://glew.sourceforge.net/ . Nothing like that for vector ?

If all header files from all vendors were the same, I could see having a central repository. While they define the standard library required api's, there are implementation details that may differ significantly.

When I had to search for the valarray header, I went to the Intel compiler root directory, and did a general find operation. I can tell you that the Intel valarray implementation has to be very different than the g++ version.

If all you wanted was the api, then there are references that provide you with what is necessary for using the api in an ordinary way. For example:
http://www.cplusplus.com/reference/vector/vector/?kw=vector
1
 
peprCommented:
This is a part of implementation of the Standard Library that comes with the compiler, so...

#include <vector>

Open in new window


For Visual C++, get the Visual Studio 2015 Community Edition plus the updates.
0
 
LuckyLucksAuthor Commented:
I have some projects have their own vector.h . So why do they do that? Are compiler specific headers a bad/non-portable thing?
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
Subrat (C++ windows/Linux)Software EngineerCommented:
vector belongs to std namespace which is the latest one So as suggested by other expert use vector not vector. h which was older one and not in std namespace. Hopefully  you will get deprecated warning if using vector. h
0
 
phoffricCommented:
In the debuggers that I have worked with, when you construct the vector or do other vector operations, you can step into the constructor. Then you will see and be able to copy the vector header file. Some debuggers may give you the folder location so that you can find the vector file, as well as other standard lib headers.
0
 
peprCommented:
It was the time when the Standard library was not that much standard, or when there were better implementations by third parties.

Notice also, that even already quite old C++ does not use .h extension for the standard library headers. If you have Visual Studio, you can find the vector header in "c:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\vector" (here for Visual Studio 2015).

In cases when there is also a C header available--like assert.h--the C++ code should use #include <cassert> wrapper instead. You should not see any .h extension for the standard headers.
0
 
LuckyLucksAuthor Commented:
@phoffric:

That is a good idea - to step into and find the src vector file.

But there is no "best policy"/ standard as to where to grab it from ? For example, if i wanted the glew headers, i would go to http://glew.sourceforge.net/ . Nothing like that for vector ?
0
 
peprCommented:
To add an illustration to the above phoffric's comment. The later C++ standard introduced rvalue references and the move semantics (C++11; for example here). This way a programmer can tell better the intention to the compiler and the resulting code is faster. When the compiler implements the feature, it can use it also for implementation of the standard libraries that come with the compiler. Say, the vector implementation becomes more efficient. If the third party vector does not use that feature, you can use it but it will be less efficient. On the other hand, you cannot use that newer implementation of the vector with older compilers that do not implement the feature.

The above description considers only the standard features. However, a compiler can use implementation details that are not prescribed by the C++ Standard. Then it may be possible to implement the std::vector even more efficiently. But then it it cannot be used for another compiler.

The Standard Library should be as efficient as it could be. This is the reason why you should prefer the one that comes with the compiler.
0
 
LuckyLucksAuthor Commented:
accepting pepr+phoffric solutions.
0
 
phoffricCommented:
Glad we could clarify this.
0
 
frankhelkCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Split:
-- phoffric (https:#a41777524)
-- pepr (https:#a41777568)


If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

frankhelk
Experts-Exchange Cleanup Volunteer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.