Release Delay
This is the first of my releases to be delayed. Sometimes these things happen, both in school projects and in software documentation updates/bug fixes. However, I decided to explain the situation instead of just hiding until it was fixed. At least this way I can get some experience from the situation.
What I was aiming for:
Correcting the Function Pointer Parameter Problem (FPPP) or, in the very least, successfully reproducing the unwanted behavior in a Minimal TestCase.
Contributing factors:
These are just some factors which helped inevitably lead to a delay, these are not excuses.
- The source of the FPPP is tricky and elusive, what works in my current Minimal TestCase doesn’t in real code. (More on this on the release)
- The machines at CDOT were down (power cut) this weekend. Now, this definitely isn’t an excuse. I read on IRC that this was going to happen, however put off copying all my testcase code and such over until, well, until it was too late.
- From the point I realized my mistake if I started from scratch I would have stayed up all night and got to the point I was at on the CDOT machines… That is, by the time I got access to the CDOT machines again. So I stayed up all night working on another project until I got access to the CDOT machines again.
When it comes right down to it I can’t *say* I have a “release” until I have something more than a testcase saying “it should work.” At the very least I want a testcase saying “this is WHY it doesn’t work,” and better than that an actual fix once and for all for the FPPP!
I strive to release quality material to the community, and will not waste both of our time trying to push over incomplete work as a release. With that, it is my plan to put out some definitive work in the next couple days.
Thank you,
-Roger Dikce
(*Now that’s practice for a press release right there.)
