sahu

 Profile Answers by sahu Questions by sahu

• Jan 5th, 2006

 

ans:

C) Both A & B

sabir

• Jan 13th, 2006

 

both r same and valid

prakash_s_nayak

 Profile Answers by prakash_s_nayak 

• Feb 23rd, 2006

 

The Answer is A X++ as it is the next increment value of X and X+=1 is it shows the initial value of X and then again an incremented value where as X= X+1 is only equal to X++.

Sreerenj

• Mar 24th, 2006

 

Both A and B are correct, but it depends on where you are using it. Same like pre and post increment (e.g. i++, ++i)

For example if you are using it like
int x = 10;
x++; // or x+=1;
Console.Write(x);

both will give the same output, but if you are using like
Console.Write(x++);
then the output will be 10 but for x+=1 then it will be 11 that means it is equalent to post increment ++x;

So the currect answer depends on the context where you are using

prakash_s_nayak

 Profile Answers by prakash_s_nayak 

• Mar 24th, 2006

 

But you did not understand the question.As this type of questions are a logical type interview question.

dotnetrocks

 Profile Answers by dotnetrocks 

• Jun 21st, 2006

 

Performance wise both the approaches are similiar. BUt consider this statement. suppose some object obj has a variable in it as i. then, obj.1 = obj.i + 1In this case at the MSIL level u can see 2 diff calls to the obj.get and obj.set property. There are 2 ldloc instruction calls in the MSIL..While if we had used obj.i += 1 then there is just one call to the obj.get property which is something better in performance if the property did many time consuming validations. Thus i think guys as far as possible try using these compount operators like +=, -= etc. Thanksdotnetrocks

samiksc

 Profile Answers by samiksc 

• Jul 11th, 2007

 

x=x+1 is equivalent to x+=1 except that value of x is evaluated only once.
x=x+1 is not equal to x++ (not always equal as mentioned in one of the earlier comments). If x++ is a standalone statement, the two have equal effect.