Bug squashed

Well, after hours of fruitlessly trying to solve the problem in some clean way, I eventually dirty hacked my way around it.  Ironically, the “clean” solution required touching six files, the “diry” solution required touching 2 lines.  I don’t like it from a logical perspective but the extra burden it imposes on customers is minimal and would require them to have non-default settings to even notice, so I guess that is survivable.  (I also checked and out of 560 word lists it affects only 8 of them.)

I think I’ll chalk this one up to “Eh, sometimes you just have to ship it.”

Now to pay my penance for slackadaisical testing earlier: new CDs for six people, who each got one with the bug on it.

Explore posts in the same categories: Uncategorized

One Comment on “Bug squashed”

  1. Rich Says:

    Customers don’t see your code. They see bugs, and how fast they get fixed.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: