RE: [gmt-dev] evolving GMT in a fully open process that allowsothers to

["Ghica van Emde Boas" <emdeboas@xxxxxxxxxxxx>]

> > The dependencies on the target
> > language (Java in this case) should be kept in template code as far as
> > possible, rather than in the structure of the model from which you
> generate.
>
> in my view, this does not really work in practice
> (at least, if you want to keep the template readable).
> Extending the metamodel with aspects is a good
> alternative.

I agree to this. And it is not only to keep the template readable. How else
would you specify that a certain attribute that is a date in your model has
to be implemented as a unix timestamp so that it looks like an INT to the
database, or a certain relationship in the model as a Java HashMap?

Regards,
Ghica van Emde Boas
Bronstee.com Software & Services b.v.
e-mail: emdeboas@xxxxxxxxxxxx,
tel: +31 23 5474422,
or: +31 6 53368747 (mobile)
fax: +31 23 5473347