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.
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)