N
Nick Keighley
the test is broken. It does not bode well for the technical competance
of the company.
Don't Do That
In a computer science exam I answered "the question you meant to ask
was ...". Since I got a good mark in this exam I assume I was right. I
think it highly likely that the OP (or someone else) mistranscibed
it). People who write tests are not god-like beings.
yes but it may not give an "error" as in a diagnstic or crash
I think the correct response is that apocryphal japanese word
"mu" ("unask the question")
hell, or even one line to another
against *all* versions of the C standrad
<snip>
of the company.
Don't Do That
So your answer is to redefine the question because you can't cope with
the problem and answers as given? You are no longer answering the
question but questioning the question.
In a computer science exam I answered "the question you meant to ask
was ...". Since I got a good mark in this exam I assume I was right. I
think it highly likely that the OP (or someone else) mistranscibed
it). People who write tests are not god-like beings.
As others have pointed out, it is undefined, therefore the proper
answer is: error.
yes but it may not give an "error" as in a diagnstic or crash
I think the correct response is that apocryphal japanese word
"mu" ("unask the question")
UB means you cannot predict what the result will be because the
standard does not define what implementations are required to do. It
is open to interpretation by the implementation, therefore you cannot
depend on the result from one implementation to another or one version
of an implementation and another.
hell, or even one line to another
The [crap code] seems to be intended to be a precedence problem where the
tester is seeking to know if the student understands pre-increment and
pre-decrement but the code is erroneous on its face when interpreted
against the current standard.
against *all* versions of the C standrad
<snip>