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.
To say debuggers take time away from development is just silly. They are another tool to have at your disposal, and sure they may not be easy to use at first, but used effectively they should put more time back into development by easing bug searches.
I also had a go at getting Farcry up and running on BD. Wading through a foreign and relatively large code base is not the easiest of tasks (especially if docs are lacking) and would have loved a debugger.
It's true that a 4GL such as CF requires less debugging than lower level languages but it's still a good tool to have. IMO lack of such tools help tarnish CF's cred amongst professional developers.
Vince you can put my vote down for a BD DB.
-- tim lucas
http://www.toolmantim.com
----------------------------------------------------------
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]
