> What if I could offer you a step debugger instead > that would > allow you to set breakpoints, examine variable scopes > anywhere in the call > stack, etc.?
I'd probably say "don't waste your time". CF used to have an integrated debugger, and they dropped it in CFMX. CFABORT might be crude, but it's very effective. Kind of like using System.out.println() over Eclipse's integrated debugger. Debuggers are hard to use effectively, and they take time away from development. Not say that they're not very valuable in some situations, but most of the time all they do is get in the way. Of course, that's 100% personal opinion. Crude illustration of the concept: "I need to kill someone. Should I bludgen them with a baseball bat, or should I carefully sedate them with <something>, bring them to an operating room, anesthetize them, make an incision into a vein of choice, and let them bleed out (while unconcious, so they don't feel anything), making sure to keep everything clean." Cheers, barneyb ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
