int i;
for(i=1;i<=10;i++)
{
      i=i*3;
      printf("%d",i);
}

int i,no;
for(i=1;i<=10;i++)
{
      no=i*3;
      printf("%d",no);
}

for(i=1;i<=10&&printf("3*%d=%d",i,3*i);i++);

Answer :
HELL%@!~@!@???@~~!

      Explanation:
The character array has the memory just enough to hold the
string “HELL” and doesnt have enough space to store the
terminating null character. So it prints the HELL correctly
and continues to print garbage values till it 	accidentally
comes across a NULL character.

Answer : 

	Garbage values.

Explanation:

	Both the functions suffer from the problem of dangling
pointers. In someFun1() temp is a character array and so the
space for it is allocated in heap and is initialized with
character string “string”. This is created dynamically as
the function is called, so is also deleted dynamically on
exiting the function so the string data is not available in
the calling function main() leading to print some garbage
values. The function someFun2() also suffers from the same
problem but the problem can be easily identified in this case.

Answer : 

		string constant 

Explanation:

		The program suffers no problem and gives the output
correctly because the character constants are stored in
code/data area and not allocated in stack, so this doesn’t
lead to dangling pointers.

Answer :  

		Variable length argument lists

Answer :  

		Compiler error: Cannot increment a void pointer

      Explanation:

Void pointers are generic pointers and they can be used only
when the type is not known and as an intermediate address
storage type. No pointer arithmetic can be done on it and
you cannot apply indirection operator (*) on void pointers.

Answer :  

		Compiler error: Too many initializers

      Explanation:

The array a is of size 4 but the string constant requires 6
bytes to get stored.

Answer :  

		Yes

      Explanation:

      The pointer ptr will point at the integer in the
memory location 0x400.

Answer :  

      	Implementaion dependent

      Explanation:

The char type may be signed or unsigned by default. If it is
signed then ch++ is executed after ch reaches 127 and
rotates back to -128. Thus ch is always smaller than 127.

Answer :  

      Compiler Error: “Unexpected end of file in comment
started in line 5”.

      Explanation:

The programmer intended to divide two integers, but by the
“maximum munch” rule, the compiler treats the operator
sequence / and * as /* which happens to be the starting of
comment. To force what is intended by the programmer,

      int k = *ip/ *jp;	

      // give space explicity separating / and * 

      //or

      int k = *ip/(*jp);

      // put braces to force the intention  

      will solve the problem.

Answer :  & Explanation:

Prefer the first one. If the str contains any  format
characters like %d then it will result in a subtle bug.

Answer :  & Explanation:

The second one is better because gets(inputString) doesn't
know the size of the string passed and so, if a very big
input (here, more than 100 chars) the charactes will be
written past the input string. When fgets is used with stdin
performs the same operation as gets but is safe.