Thomas Fischer wrote:
> 1) Do we want to use the proposed code generator in torque ?
+1
> 2) If 1 is positive, should the code generator be inside or outside of
> Torque ?
Inside, if I were to decide. We can still see what evolves later on.
Bye, Thomas
---
Greg, Thomas,
Thanks for your reviews and opinions.
Greg Monroe wrote
> ...
> My first concerns are that this seems to be fairly complex and that as a
core
> part of Torque, there is a risk of overall reliability going down.
>From my "inside perspective", the code generator is not very complex.
Thomas Fischer wrote:
> To explore what such a code generator could look like and whether it can be
> implemented at all, I have developed such a code generator, with the
> intention to include it into torque. The code proposal and a site with the
> features and a short introduction can be found he
inside... and moving it out as it
matures.
> -Original Message-
> From: Thomas Fischer [mailto:fisc...@seitenbau.net]
> Sent: Wednesday, November 11, 2009 2:42 PM
> To: Apache Torque Developers List
> Subject: Re: [Proposal] A general-purpose code generation framework for
> torqu
Following the question of whether or not add @SuppressWarnings in the
generated source code, I have used this as a showcase for the proposed
generator, showinh how to change the generated output without touching the
original torque templates.
The main idea is that one template-set (in this case a
This is a proposal to replace the current torque 3.3 code generator with a
general purpose code generator, which would be developed inside the torque
project.
The torque 3.3 code generator has, in my eyes, the following shortcomings:
- It is not possible to modify the templates locally (i.e. in o
