Ahmed Mohombe wrote:
Sounds a bit like trails, doesn't it?
Nope :). AFAIK The main idea of Trails is NOT to generate code :), but
to "reflect" what's required,
using mostly annotations.
I see a lot of people seem to see the same similarity I saw, but you've
probably given it a lot more thought so...what's the upside of
generating code instead of reflection, regardless of the level of
abstraction I use the term?
Generally speaking, code generation is not something a programmer should
welcome with open arms - I've heard people say something along those
lines, I got burned a couple of times myself, I've seen some of the
problems. Still, it can be used to solve problems. What would be the
main difference between AMAGe (Ahmed Mohombe Application Generator :-))
and Trails and would that justify going about a completely new framework?
t.n.a.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
