Menu
I posted a question with my code whose only #include directive was the following:
#include <bits/stdc++.h> My teacher told me to do this, but in the comments section I was informed that I shouldn't.
Why?
478
So, when we use shouldn't I instead of should I not, we mean so to say that things in fact were not wrong, but perhaps unnecessary. The same I meant saying that when I pronounce variants where "not" put after pronoun it sounds more serious and solid, than when we use shouldn't.
"Why would I X" is asking for the reasons that would force you, lead you, or make you do X. "Why should I X" is asking for the reasons that you would voluntarily choose to do X. A speaker/writer may not know that someone actually has or doesn't have a choice in something, so they may use the "improper" word.
Can't is a contraction of cannot, and it's best suited for informal writing. In formal writing and where contractions are frowned upon, use cannot. It is possible to write can not, but you generally find it only as part of some other construction, such as “not only . . . but also.”
-- Correct, we should not. In three out of four of these cases should is being used to express obligation or what is the correct action. Should we not. is the only case where the meaning is shifting to the conditional sense of the word should.
Including <bits/stdc++.h> appears to be an increasingly common thing to see on Stack Overflow, perhaps something newly added to a national curriculum in the current academic year.
I imagine the advantages are vaguely given thus:
#include line.Unfortunately, this is a lazy hack, naming a GCC internal header directly instead of individual standard headers like <string>, <iostream> and <vector>. It ruins portability and fosters terrible habits.
The disadvantages include:
Don't do it!
More information:
Example of why Quora is bad:
174
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With