If you needed a little more info that the SQL already contained you could have added it in there, eg. in the form of some specialy formated comments. That way your users do not have to learn a whole new "language", just a few additional attributes. And if someone does have the SQL ready, he/she doesn't have to rewrite it into XML to be able to use your generator.
I would prefer
tocreate table occupation /*#descriptor="description"*/ ( description varchar(40) not null /*#caption="occupation"*/, comments text )
anytime. But that's maybe because I would prefer anything to XML.<table name="occupation" caption="occupation" descriptor="description" +> <field name="description" type="varchar" size="40" notnull="1" cap +tion="occu +pation"/> <field name="comments" type="text" caption="comments"/> </table>
Jenda
Always code as if the guy who ends up maintaining your code
will be a violent psychopath who knows where you live.
-- Rick Osborne
In reply to Re: Code Generation in Perl
by Jenda
in thread Code Generation in Perl
by nferraz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |