It would be interesting to know how the whitespace (tabs vs spaces) before the extra goto compares to that on the other goto lines. This might provide a clue as to whether copy/paste was involved.
On the subject of how the extra line appeared in the first place, my take on possible causes are, in order of likelihood:
1. Line added during developer testing to force a fail and not removed.
2. Copy/paste error during construction.
3. Artefact from a bad code merge.
4. Deliberately introduced by NSA mole.
Presumably, one someone goes through the version control history, the who and when will be known - though maybe not publicly. I'm not sure we'll ever know why, though.
It would be interesting to know how the whitespace (tabs vs spaces) before the extra goto compares to that one the other goto lines.
(in case anyone is curious, the "goto fail" lines in that part of the code are identical: all spaces; and the file in general does have an unfortunate mishmash of spaces and tabs)
Comments
It would be interesting to know how the whitespace (tabs vs spaces) before the extra goto compares to that on the other goto lines. This might provide a clue as to whether copy/paste was involved.
On the subject of how the extra line appeared in the first place, my take on possible causes are, in order of likelihood:
1. Line added during developer testing to force a fail and not removed.
2. Copy/paste error during construction.
3. Artefact from a bad code merge.
4. Deliberately introduced by NSA mole.
Presumably, one someone goes through the version control history, the who and when will be known - though maybe not publicly. I'm not sure we'll ever know why, though.
(in case anyone is curious, the "goto fail" lines in that part of the code are identical: all spaces; and the file in general does have an unfortunate mishmash of spaces and tabs)