What was supposed to be 0.8 Release

*Note: This is a somewhat incomplete version of what my 0.8 release post was going to be. It isn’t full of links, and probably doesn’t make sense sometimes. However I thought there might be some information worth sharing in it., so I am sharing it anyway.

This “release”

This release [was supposed to be] an attempt to reproduce the incorrect behavior Dehydra (or the analysis script I was using) displayed when generating docs for external string in Mozilla. The reproduction was to take place in a minimal testcase to help show exactly where the error was occurring. However once I built my own analysis script from scratch everything worked as it should. Trying to get closer to what the erroring script analyzed, I set up an example similar to the way the the Mozilla code was written. In this case my first analysis script failed altogether not displaying the information I wanted nor the errors I was looking to reproduce. I then realized my analysis script was working in a much different way than the original script I was looking to fix. I analyzed the original script by hand and attempted to narrow it down to one of the methods it uses for analysis which also produces the error results. I decided going through gdb might be a good idea.

Good things this release

Got a hold of Taras who pointer me toward a Minimal TestCase. Though I think he might expect me to file a new bug for him to take care of.

Learned about Minimal TestCases!

Learned about JSLib!
Became reacquainted with X11 tunneling!
Realized the two above were a waste of time when I thought, “Wait… How does this script run via Dehydra?” and read the docs.
Discovered my new friend write_file(filename, data); to write to a file from JavaScript using Dehydra.

Bad things this release

Delaying the release by days.