My post is unedited as yet. Show me the word "must".
People do not change their strongly guarded opinions/habits/nature etc. So, I am not trying to persuade everybody into using my type of coding style. You are doing this. Including in your own signature. Saying to all and sundry. Use int main. Don't use scanf.
I did not say it contains must. But you worded it like a command, ie - similar to "must".
There is a difference. Void main is undefined, non-standard, or in other words, it's not C OR C++. It's "special C/C++" - something that does not exist and should never be used.You are doing this. Including in your own signature. Saying to all and sundry. Use int main. Don't use scanf.
Scanf can read strings, but you must do it right or you can very easily get buffer overruns. And why is that bad? Because it's a security issue plus it's undefined - anything can happen, including corrupt data in the program or crashes. Don't come to me complaining "why isn't this working?!" when you have a buffer overrun somewhere that might overwrite your variables.
Coding styles are different. They are not required by the language or undefined.
There is no need, since those statements were clearly instructions. In other words, "must" is inherent in the context.My post is unedited as yet. Show me the word "must".
Yes, but in your original statement, it is quite clear that you were not trying to persuade everybody, but was commanding the original poster to use the given style. That is what Elysia is getting at.People do not change their strongly guarded opinions/habits/nature etc. So, I am not trying to persuade everybody into using my type of coding style.
Elysia's signature does not tell people to use Elysia's style, but to follow the standards and to avoid specific functions. There are objective reasons to avoid those functions, unlike your subjective "arrogant" reason.You are doing this. Including in your own signature. Saying to all and sundry. Use int main. Don't use scanf.
Look up a C++ Reference and learn How To Ask Questions The Smart WayOriginally Posted by Bjarne Stroustrup (2000-10-14)
I do not think so. Otherwise I would not need to prove Elysia wrong.
Commanding!? Oh come on please! You are not a native English speaker I think.Yes, but in your original statement, it is quite clear that you were not trying to persuade everybody, but was commanding the original poster to use the given style. That is what Elysia is getting at.
Me neither.
Should/Ought to - is used as a suggestive of helpful/useful
Must - is used for compelling/forcing making it a rule
I did not use should/ought to. Beacuse I did not think my suggestion were more useful, than any other consistent guidelines.
Must I can never use. I can't force any body to do any thing at all.
I just wrote in plain declarative sentences without any kind of obligatory means at all.
No I am not good at English. Spoken. Written. Or Grammar.
Standard must have vaild reasons to allow compiler extensions. C++ does not even need an explicit return from a function defined as returning int. I am talking about main(). Why bother.Elysia's signature does not tell people to use Elysia's style, but to follow the standards and to avoid specific functions. There are objective reasons to avoid those functions, unlike your subjective "arrogant" reason.
But in my separate, personal, not related to this discussion, opinion, Elysia's signature is not a think to poke a stick at. I am missing the "times quoted" count though.
"Do not",
"always",
"name them"
Tell me how those are not commanding.
I think you need to brush up on your english skills. Though I may not be native english, I know well enough that it sounds commanding.
Post that somewhere else and see how people reacts.
It is commanding, because you failed to specify that it was a suggestion or guideline.
No, you're wrong. That's C. C++ does not support any implicit returns.Standard must have vaild reasons to allow compiler extensions. C++ does not even need an explicit return from a function defined as returning int. I am talking about main(). Why bother.
Does the standard allow extensions? The standard can neither approve nor disapprove extensions. That's something only the compiler makers have power over.
Although I was never commanding anybody for anything. But now I reread all the other replies up to my post. And see one difference in those and my reply. All of them used First Person Pronouns to specify their suggestions. I did not use any Pronoun at all. And most people are interpreting my sentences as being used Second Person Pronoun, and they think the Second Person is OP and the sentences are commands to him.
What a Fish!
But I have already told you all, I am also not a Native English. And I never got good marks in English Grammar.
What a pity!Does the standard allow extensions? The standard can neither approve nor disapprove extensions. That's something only the compiler makers have power over.
Manav is right in a way except, Manav, you must realize the informal nature of the board and the internet in general. You are quite right if you say you aren't a native english speaker because what you learn formally in english as a second language is not fully applicable on the internet.
If you were writing a formal speech I would agree with you, but remember it's also the way in which you present what you are saying. In your case it's like you wrote a law on C
The internet english is almost like a secondary vulgar. So if you use the word 'should' or say 'do this', it's taken as a command not a suggestion. To me it sounded like you were telling people they 'must' do something even though you didn't explicitly use the word 'must'.
Remember, it's also the tone that sets what you imply, not just the words in itself.
Who cares now, let's all get over this.
Last edited by JFonseka; 05-26-2008 at 08:21 AM.
=========================================
Everytime you segfault, you murder some part of the world
Well I think it was these words that made it sound like commandments:
Originally Posted by manav