While the quiz says all answers were "D: I don't know", the real answer for me is "I don't care" because those cases were really retarded and had no context to show what the purpose was outside of it being a pedantic case to show you don't know what the answer is. I have been in interviews that put emphasis on these sorts of cases during the technical skills tests. They were tricks to get to know how you approach a problem when you don't know the answer, but they always proved to me that their method was as flawed as the possible incorrect answers. A good programmer would change the game around the case to avoid getting into such a mess in the first place. This is a trap for beginners rather than a good test of C programming skills. You won't learn anything from these exercises if you don't learn how to avoid having to deal with them at all.
The other way to look at it is if you know how the compiler works, there is an answer. The compiler will resolve to an answer. You are correct in that the questions are designed to see how much someone knows about how the language works and how the compiler treats it.
When I'm being interviewed and I see a questions like that, generally I understand what they're looking for and I'll say, it depends on the compiler. My interview approach is to use techniques like writting a simple threading question and ask what's the value of X to see if the candidate picks up on the threaded nature of the code. If can get some pretty bad code if people write code for threaded applications and don't understand mutex, locks and synchronazation.
(post is archived)