Fixing a bug

[JimKasson]

For the last month, I've been trying to fix a bug in some code I'm using that I wrote about a dozen years ago without success. I've been creating workarounds in the absence of a real fix. Night before last, I woke up about two with what I thought was the answer. The code was fine, but a configuration parameter was set to a default value that had undesirable side effects in some circumstances. Turning that function off fixed things.

The offending parameter, with comments added to identify the problem. Programming is a conversation with the computer, and also with your future self.

--
https://blog.kasson.com

 

[Bags27]

very, very cool, Jim.

I wake up a lot in the middle of the night and scribble furiously on a pad I always keep by our bed about whatever book I'm writing at the time. In the morning, sometimes when I read it, I'll think: wow, that's the key to the argument. Most times, however, I'll say: what a bunch of crap!

 

[just Tony]

I'd tell you which one I like better but with my luck it might turn out to be the "before the fix", failed one. These are visually arresting, I feel like I'm flying over some exotic forest.

Am I to understand that those images can be created with merely 13 lines of code? Please tell me that's just one function out of a much larger body of code.

 

[JimKasson]

I'd tell you which one I like better but with my luck it might turn out to be the "before the fix", failed one.

They are both after the fix.

These are visually arresting, I feel like I'm flying over some exotic forest.

Am I to understand that those images can be created with merely 13 lines of code? Please tell me that's just one function out of a much larger body of code.

There are about 5000 lines of code involved in this processing. I posted only the properties for one of the classes.

 

[darinb]

A smell of petroleum prevails throughout.

--Darin