To what extent is the code that these tools normally generate?  What I was picturing in my head was something that more or less "spit" out a very basic structure like maybe the .CFC file with the CFFUNCTION and CFARGUMENT tags but not really much if anything beyond that.  So not even something that could  be use in a prototype but more something that could be built from.  The word "generate" though almost implies to me something that would "spit" out something similar to what data modeling tools do which is all the scripts to make a database.

On 7/25/05, Gary Menzel <[EMAIL PROTECTED]> wrote:
 
So, I think tools should be used to do the designs.  The commonality of the representation of the thoughts and ideas of how a system is to be built is a hugely important factor.  And, I guess, generated code can be used as a prototype.  But then you build.  If there are discrepancies in what is being built - then the designs either dictate the outcome, or (via peer review of both the code and the design) you agree to change the design.  You then need to re-factor the code.  The tools do a poor job of this because they can't think like people do.  Many factors can impact this process (such as optimisation).  And that is where generated code falls down - in my opinion.
----------------------------------------------------------
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