CBFalconer said:
Screw ups:
1. Posting via google and losing all indentation. See sig.
2. Failure to #include <stdio.h>
3. Lying to the compiler about the type of i in the printf.
4. lack of blanks within the code (foolish style).
Either of 2 or 3 result in undefined behavior.
As well as excessive abbreviation. In the subject, it's "be" not "b".
In the body of the article, "output" is much clearer than "o/p".
I understand there's a common writing style that uses very short
abbreviations like "4" for "for", "2" for "to", and so forth. Please
don't use that style here in comp.lang.c.