So I was doing a little testing this afternoon on some Serial communication auto-configuration logic I had written for work, and things that I had previously thought were working kept failing. This stuff is asynchronous six ways to Sunday, so I reverted back to the tried and true method of debugging — print statements. Unfortunately, the delay caused by the IO corrects the problem I had been witnessing. The next few days are sure to be fun as I try to figure out what kind of race condition I’m looking at. Good times.
I recommend utilization of “goto”. I can’t think of a programming problem that the “goto” command doesn’t solve.
So…how much of a delay are we talking here…I mean, if it fixes it…
Also, is this in that C# gibberish you keep extolling?
Ok, solution:
Since it works when you’re doing print statements just pepper the code with Console.Write(“”) all over the place. Bam. Ghetto-rigged nicely.
Exactly.