Whew

Richard A Dalton

When a debug message conveys Relief, you're probably on thin ice.

dbg('Function returning true...');
dbg('Whew.... Its your baby now - messaging');

-Rd

Chris Meech

Similar to this one

TRACE("Shouldn't be able to reach this code! But good luck, though.");

:cool:

Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]

fjdiewornncalwe

MsgBox( "Oops." ) I found this one in something I wrote in my first job out of school.

BillW33

Yes, that kind of thing is always a bad sign. Not that I ever did such a thing when I started out! ;) I do make sure to avoid doing such things now.

Just because the code works, it doesn't mean that it is good code.

Richard A Dalton

In my first job I was working alongside some guys from an external vendor. Integrating their system into ours and trying to get the whole thing validated by System Test. One day an error popped up that originated in the Vendors Code: "The System Has Gone Pear Shaped" System test weren't impressed. The guy from the external vendor was summoned, and asked what a more accurate error message would be. I can't remember what it was, but he gave a very detailed, accurate and completely unintelligible response. To which the head of system test replied... "And what does that mean? In English?" To which he replied... "The system has gone pear shaped." -Rd

JHizzle

I used to do that alot in crazy if else statements that shouldn't have been needed:

Response.Write("Something has gone seriously wrong here, please reboot universe")

RugbyLeague

I use a throw with a similar message - mostly on the default of a switch

Gary Wheeler

At which point, you take the vendor outside the building, put two bullets in his head, and leave his body mounted on a pike outside the castle walls as a warning to others.

Software Zen: delete this;

Richard A Dalton

Gary Wheeler wrote:

At which point, you take the vendor outside the building, put two bullets in his head, and leave his body mounted on a pike outside the castle walls as a warning to others.

Actually that particular project I had no problem with the Vendor. I was young Naive, what did I know? I'll say this. Compared to experiences I've had and am still having with vendors, that project was a cakewalk. When you've debugged a vendor's Javascript files you start to understand that a dodgy error message is no biggie. There's nothing quite like javascript files which seem to have had all whitespace sucked out of them, presumably to stop people stealing some of the most horrible code ever written (why would anyone want to). -Rd