cfdump is all very well but until you've used something else, you don't realise how clumsy  these ham-fisted (cfdump/cfabort) debugging methods are.

I found debugging C code on Unix (command line) more efficient than cfdump/abort. I guess every language has it low points. Debugging just happens to be a big one for CF. PHP has even got better support for debugging.
 

If Visual Interdev 6.0 could debug ASP pages in 2001 then surely in 2005 a CF editor can have the same sort of features...

From what I read, CF pre MX use to be able to do it. I must have something to do with the new architecture. Maybe someone at MM knows the reason why it seems to have been dropped.
--- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to