from what i've heard, c transforms expr1[expr2] in *(expr1+expr2), right?
but this is madness it means that you could, for example, say:
i++[x]; // where x is a array (pointer)
seems crazy to me. Is it correct?
2nd thought: if it IS correct, then how will you obsfucate multi dimenssional arrays? j[i++[x[k]][l] ??? how does the compiler know which is the column or the line?
this is really madness now...
Two strings walk into a bar. The first one says, 'Bartender! Bartender! I want a drink!'. The second one says, 'Bartender! Bartender! I want a drink too! Blaaaaaaaaah eeeeeeeek yaaaaaaak oooooooh'. The first one says, 'Please excuse my friend. He isn't null term--'.
Here's a good reference.
Quzah.
Hope is the first step on the road to disappointment.
well, i found out that i++[x] is correct, but i'm still not clear about obfuscated examples. does any compiler has its rules?
Two strings walk into a bar. The first one says, 'Bartender! Bartender! I want a drink!'. The second one says, 'Bartender! Bartender! I want a drink too! Blaaaaaaaaah eeeeeeeek yaaaaaaak oooooooh'. The first one says, 'Please excuse my friend. He isn't null term--'.
also about obfuscated things, look at the following example:
*++b ? (*++b + *(b-1)) : 0
b-1 is calculated with b or with ++b ?
i'm just asking because i've come across some 'nice' code...
Two strings walk into a bar. The first one says, 'Bartender! Bartender! I want a drink!'. The second one says, 'Bartender! Bartender! I want a drink too! Blaaaaaaaaah eeeeeeeek yaaaaaaak oooooooh'. The first one says, 'Please excuse my friend. He isn't null term--'.
Why are you even bothering with this stuff?
1. Changing a[i] into i[a] has NO practical applications, so whilst it's a curiosity, it's not useful enough to worry about.
2. *++b ? (*++b + *(b-1)) : 0
Read the FAQ which Quzah posted (all of it).
Find out why all expressions with multiple side effects are undefined, no matter how 'nice' they are.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
well, just asking... i'm not using them don't worry.
Two strings walk into a bar. The first one says, 'Bartender! Bartender! I want a drink!'. The second one says, 'Bartender! Bartender! I want a drink too! Blaaaaaaaaah eeeeeeeek yaaaaaaak oooooooh'. The first one says, 'Please excuse my friend. He isn't null term--'.
Isn't this statement okay?Originally Posted by Salem
Isn't b only modified once in between sequence points?Code:*++b ? (*++b + *(b-1)) : 0
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
Which happens first, *++b or *(b-1)?
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
http://www.cppreference.com/operator_precedence.html
Seems simple enough. (b-1) would be evaluated first.
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
>Seems simple enough. (b-1) would be evaluated first.
Or perhaps second. There's no guarantee.
I believe the order of evaluation for binary + is unspecified, so either one could happen before the other.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
After playing with it and reading back through previous threads, I see that I was totally ignoring the following sentence: "Between the previous and next sequence point an object shall have its stored value modified at most once by the evaluation of an expression. Furthermore, the prior value shall be accessed only to determine the value to be stored." Makes sense now.
If I did your homework for you, then you might pass your class without learning how to write a program like this. Then you might graduate and get your degree without learning how to write a program like this. You might become a professional programmer without knowing how to write a program like this. Someday you might work on a project with me without knowing how to write a program like this. Then I would have to do you serious bodily harm. - Jack Klein
