I'm using it, and I have seen a message or 2 fly past in the DOS window
about syntax errors or something, but i haven't paid any attention to them,
as they referred to some legacy code that i knew was broken anyway.

You can output the log messages to a file, and that's what i'd suggest doing
if you want to try to use cfcompile for this purpose, but in my limited
experience, i have no idea how useful that would pan out to be. That and use
a batch file so you don't have to type out the syntax every time.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Dave Merrill
Sent: Saturday, May 14, 2005 3:35 PM
To: [email protected]
Subject: RE: [CFCDev] CFC wish-list


I haven't explored mx7's cfcompile tool, but I'm wondering how much it
catches what would otherwise be runtime errors. Even if you didn't want to
deploy with it, just running it as another form of testing might be
beneficial. Certainly that's true in other languages.

Are people typically trying that? Comments?

Dave Merrill




----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).

CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm

An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]






----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to