If you do not specify a return type for main(), it does not mean you are exempt from returning a value. This feature is called implicit int. It means that if a data type is expected but not provided, int is assumed. So these two definitions of main() are exactly the same and the return statement is required for both:
Relying on implicit int is not a good practice because the latest C standard removes the feature. Your code will not compile as C99, and that adds one more thing that needs to be changed to make it conform.
Names in all upper case are usually reserved for macros. It is up to you whether or not to use that convention, but people reading your code will be confused that STR1 is an array object and not a macro.
clrscr() is a non-standard function from conio.h, but you did not include conio.h. I would not recommend anything from conio.h, but like the naming conventions, it is up to you whether or not to take that advice. The portability police will not haul you away if you choose to use unportable stuff.
gets() is always unsafe and cannot be made safe through good coding practices. Never use it, because there is always a risk of array overflow. The safe alternative to gets() is fgets():
fgets(STR1, sizeof STR1, stdin);
for(i=strlen(STR1)-1; i>=0 ; i--)
{
printf("%c",STR1[i]);
}
In C you should always make sure the output stream is flushed by either printing a line break or calling the fflush() function. It is possible that the output for your program will not show up before getch() starts waiting for input. It will look like the program is hanging. You can easily fix the problem and make the code work everywhere by printing a line break after the loop:
for(i=strlen(STR1)-1; i>=0 ; i--)
{
printf("%c",STR1[i]);
}
putchar('\n');
getch() is in the same category as clrscr() except there is a portable function from stdio.h that can replace getch() called getchar(). The only difference is that getchar() will probably not return until you type [Enter].
Offline 
Marked 
