By nick_l
via spokedweb.com
Published: Oct 04 2007 / 19:02
Discussing different pitfalls and traps of using code generators
By nick_l
via spokedweb.com
Published: Oct 04 2007 / 19:02
Comments
dzonelurker replied ago:
There are 100 reasons why Code Generation rocks!
nick_l replied ago:
Yes, but the good aspects are well understood and I don't think people appreciate the disadvantages of poorly done code gen.
Dmitriy Setrakyan replied ago:
Yes, and there is a 101 reason why Code Generation sucks :) I am yet to see a case where code generation offers more than it takes away.
sandbergc9 replied ago:
Here is a simple case. I have a database with tables and fields, i want each table to be represented one to one to a class with the same attrinbutes ( as the table's fields).
I connect middle gen to the database, select my tables and clicj on generate and I have a nice set of classes with attributes and setters and getters.
Save me a lot of typing, and the classes are cleanly written.
I've use this many times on new projects!
peimei replied ago:
I have no compaints with my Rails generators (or the generators I have written for Rails). You just have to understand that generators are not the total answer, they are a tool to get you up to speed quicker and should only be used to replace redundant tasks.
Voters For This Link (13)
Voters Against This Link (7)