-> NOT using int main() == not good

i agree

BUT

I think i am right in this case. I dont have anything against int main(). But if we dont have to use it , we should make our life simple in terms of compiling. Because if your int main() doesnot have return 0; , you might get a warning or error in any C compiler in the world.

Some material to have a look at:
int main() vs void main()

http://www.eskimo.com/~scs/readings/...in.960823.html

So i agree with you , that i should use int main() , but a small program like printing ASCII and integer doesnot need that much of attention. :)

>/* I dont think my main should return an Integer*/
It doesn't matter what you think. You still have to follow the rules. If you don't like it, go to C99 or C++ where 0 is returned automagically. And if you use C99, be sure to tell us so you don't get blasted for failing to return a value[1].

>I think i am right in this case.
I know you're not.

>But if we dont have to use it , we should make our life simple in terms of compiling.
That's the thing, you do have to use it unless your compiler offers an alternative. If your compiler doesn't offer an alternative, the behavior is undefined. You can't win this battle because nobody who's qualified to have an opinion on the matter will agree that saving a trivial line of code is worth undefined behavior.

>Some material to have a look at:
I've read it, but thanks anyway.

>So i agree with you , that i should use int main() , but a small program
>like printing ASCII and integer doesnot need that much of attention.
Rationalize it however you like, but I won't trust your code, and I'll encourage other people not to trust your code, because if you're that sloppy with a small program, who knows what kind of crap you write in larger programs.

[1] Of course, you'll probably still get blasted by the people who think it's a bad practice.

lol,

I am not a Software engineer but i am an electronic engineer. I have done C++ and i am a Java addict. i know other languages too. But my point is , i am not doing anything wrong by putting void main (void)
I have done parallel to LCD interfacing using C. And if you call my void main sloppy , then that sloppiness worked. Saying this that i am wrong by using void main , is not acceptable, if its wrong it shouldn't work , but its compiling and running.
i admitted that you are right , but you cant say i am wrong and say my code is not trustable.

How many times are you prepared to run across the road blindfolded, just because you managed to get across the first time without being run over?

Being right is a matter of attitude to solving the problem, not what your current compiler will let you get away with. Of course your next compiler may be a lot less lenient, but by then the damage has been done and you have to unlearn a bunch of crap (I know, I've been there).

Makes sense,
thanks Salem ;)

>But my point is , i am not doing anything wrong by putting void main (void)
Do you honestly believe that you're not doing anything wrong by breaking an explicit rule?

>i admitted that you are right
No, you agreed with me superficially and then went right back to saying that your way isn't wrong.

I'm sorry Software guy, but you're a bad programmer and you shouldn't be writing code until you understand the problem with "it works for me" arguments.

ok

i used a this code:
int x;
x=getch();
printf("%d",x);

#include<stdio.h>
int main()
{
char ch;
int x;
scanf("%c",&ch);
x=ch;
printf("%d",x);
}

Two resurrections of a 3-year old thread with worthless posts are enough. Closed.