Glad I could ?help?.
-Bill
www.brainbox.tv
----- Original Message -----
From: "Hubert Earl" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, May 04, 2001 10:30 PM
Subject: Re: What's the best way to deal with inexplicable error messages?
> Hi,
>
> Thanks for the feedback. Having just solved a problem largely due to my
> taking some time away from it, I'm seeing the value of the recommendation
> you made in the first paragraph of your email below. I discovered that
the
> problem wasn't at all the kind I'd been thinking it was, and taking 'time
> out' allowed me to get a better perspective on it.
>
> Hubert
> ---
> Hubert Earl
>
> ICQ#: 16199853
> AIM: hubertfme
>
> My Jamaican Art, Craft & More Online Store:
> http://www.angelfire.com/ny/hearl/link_page_on_angelfire.html
>
>
> ----- Original Message -----
> From: "Bill Davidson" <[EMAIL PROTECTED]>
> To: "CF-Talk" <[EMAIL PROTECTED]>
> Sent: Friday, May 04, 2001 6:48 PM
> Subject: Re: What's the best way to deal with inexplicable error messages?
>
>
> > From someone who has written code the majority of my life (usually for
> > pleasure more than anything), the best thing to do is take some time
away
> > from the problem. Not a lot, just enough so you're not seeing red. If
> you
> > are frustrated, you're not going to be productive. Go back later, and
> > document your code as best as you can. Document every friggin' line if
> you
> > have to. See if your algorithms & methodologies make sense.
> >
> > Then start debugging. I have never REALLY been able to get debugging
> going
> > in CF Studio. That's one thing I'd love to rectify...
> >
> > Comment out sections of your code until you get a page that works. You
may
> > have to substitute the commented out code with strict setting of values
to
> > replace logic that otherwise exists. Start isolating the problems, and
> you
> > can always add your own debugging code, like variable testing, and
> > CFOUTPUTing your values as you go.
> >
> > This is also where a methodology like OOD (in other languages) or
Fusebox
> > (in Fusebox) helps a lot - you can isolate problems pretty quickly. My
> > fusebox code is so segmented that I can quickly see where the error is
> > occurring. It helps to have debug output on.
> >
> > Also, error messages/crashes in debug mode in compiled languages/etc
> should
> > be the easiest kind to fix as it tells you exactly where in the code
> things
> > are blowing up. Logic bugs are the hardest to deal with. They're a
tiny
> > bit of the reason I can't quit smoking. ;)
> >
> > -Bill
> > brainbox
> >
> > ----- Original Message -----
> > From: "Hubert Earl" <[EMAIL PROTECTED]>
> > To: "CF-Talk" <[EMAIL PROTECTED]>
> > Sent: Friday, May 04, 2001 4:56 PM
> > Subject: What's the best way to deal with inexplicable error messages?
> >
> >
> > > Hi,
> > >
> > > What's the best way to deal with inexplicable error messages? Is it:
> > > a. to slog away at the problem until the solution is found?
> > > b. to do something else, then come back after a while?
> > > c. to redo the code from scratch?
> > >
> > > I'd appreciate words of wisdom from cooler, more experienced heads,
> since
> > there *must* be a way to avoid the enormous frustration I often feel
while
> > coding! :-)
> > >
> > > Hubert
> > > ---
> > > Hubert Earl
> > >
> > > ICQ#: 16199853
> > > AIM: hubertfme
> > >
> > > My Jamaican Art, Craft & More Online Store:
> > http://www.angelfire.com/ny/hearl/link_page_on_angelfire.html
> > >
> > >
> > >
> > >
> > >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
