Headers module #74
Headers module #74
Conversation
|
|
||
| #### Background/Required Knowledge | ||
|
|
||
| * All of the above. |
There was a problem hiding this comment.
Is "All of the above" on line 77 referring to all of the foundational background? I think that it would be clearer to say this explicitly. Incidentally, is it implied that all background for a topic at the foundational level is also required for the main level? If so, then perhaps such a statement is unnecessary?
Would like to get cross-references in advance section to other modules which are coupled to headers, such as classes, templates, modules, etc.
|
/ok-to-test |
feeling of small-group was to omit advanced section, as each advanced topic seemed more relevant to a different module
rwdougla
changed the title
| * Usage of standard library code requires inclusion of various header files | ||
| * Give examples of various header files and when they may be needed for inclusion | ||
| * Include links to reference materials for finding out what headers are used for various feature sets | ||
| * When using standard library facilities, can either use `using std::vector; vector<int> v;`, or `std::vector<int> v;`, or `using namespace std; vector<int> v;`, though modern practice strongly discourages invoking `using namespace std;` |
There was a problem hiding this comment.
That is a nice example but that does not relates to headers. I think it relates to templates and I am not sure if we should mention it there.
Thoughts?
There was a problem hiding this comment.
From what I see, this relates directly to headers. The reasoning this point tries to get across is the fact that using namespace x, in a header introduces all names within x into all files that include the specific header (even transitively). This not only makes it likely to have name clashes but also increases the chance that, for example, some usages of functions with the same name as is present in x, select a different (better fitting) overload, which can introduce subtle errors.
I assume, @rwdougla wanted to have this point covered when talking about headers, so that students are aware and do not misuse using namespace x.
Maybe we should highlight the reasoning here so it's clearer.
|
@rwdougla could you please have a look and accept the changes? |
|
@vulder Perfect. Thanks. We will work next week on the lambda pull request. |
resolves #3