Quote:but my code is TERRIBLE! ! !
Indeed, terrible is the word.
You start with 1 idea (currentGap, largestGap, binaryGap), then switch to another idea in the loop, then come back to first idea when trying to spit out the result.
A complete rewrite is in order.
Advice: Solve the problem by hand, write down how you have done, solve problem again by applying the procedure, change procedure as needed.
When procedure works, it is your algorithm, write code accordingly.
In order to help you understand how your code behave, use the debugger and watch it perform.
Your code do not behave the way you expect, or you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.
Debugger - Wikipedia, the free encyclopedia
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide
Basic Debugging with Visual Studio 2010 - YouTube
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.