![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Rantage behind the cut, due to excessive whining and massive thrashing about like a giant petulant baby.
Why can't I just once write a program that doesn't contain some imbecilic, trivial programming mistake that costs me a couple of hours of debugging, at least, before I finally catch it, punch myself in the face for being an idiot, and fix it? The problem rarely if ever seems to be that I'm just flat out misunderstanding the algorithm, although that tends to be the first conclusion to which I jump as I'm debugging it. Last time, it was not accounting properly for floating-point error that bogged me down. This time, it was a stupid loop condition being off by one.
As a hint, for those in the know, here was the problem this time:
I had this for some damned preposterous reason:
for(unsigned i = 0; i < poly_table.size() - 1; ++i)
when I should have had this:
for(unsigned i = 0; i < poly_table.size(); ++i)
*punches self in face*
On the bright side, all my polygons are now drawing correctly without ridiculous looking holes in them, at least. Now all I have to do is maybe make some optimizations, and write the report, but that can certainly wait until tomorrow.
Why can't I just once write a program that doesn't contain some imbecilic, trivial programming mistake that costs me a couple of hours of debugging, at least, before I finally catch it, punch myself in the face for being an idiot, and fix it? The problem rarely if ever seems to be that I'm just flat out misunderstanding the algorithm, although that tends to be the first conclusion to which I jump as I'm debugging it. Last time, it was not accounting properly for floating-point error that bogged me down. This time, it was a stupid loop condition being off by one.
As a hint, for those in the know, here was the problem this time:
I had this for some damned preposterous reason:
for(unsigned i = 0; i < poly_table.size() - 1; ++i)
when I should have had this:
for(unsigned i = 0; i < poly_table.size(); ++i)
*punches self in face*
On the bright side, all my polygons are now drawing correctly without ridiculous looking holes in them, at least. Now all I have to do is maybe make some optimizations, and write the report, but that can certainly wait until tomorrow.
