I agree that we should try to keep this in the code.
With my other suggestion of eventually having pluggable enforcing, we
should perhaps collect the rules behind some interface. In that way we
will achieve both the "one place" and the "keep in code" requirements.
Perhaps each programming language would come with a set of critics and
enforcing rules.
/Linus
> -----Original Message-----
> From: Tom Morris [mailto:[EMAIL PROTECTED]
> Sent: den 7 februari 2007 08:10
> To: [email protected]
> Subject: RE: [argouml-dev] Wellformedness rules - enforcing vs critics
>
> I'd prefer to see stuff like this documented in the code to which it
> applies
> (if there's more than one place, that's a different problem). The
> cookbook
> is too large and too rarely consulted for this kind of design
information.
> It'll never get seen there.
>
> The problem with enforcing rules strictly and immediately is that it
> doesn't
> allow the user to create partial models which invalid or models which
are
> inconsistent during the process of changing them. The flip side of
that
> is
> that defering resolution of the issue increases the likelihood that it
> will
> never get addresses. It's a balancing act and I'm not sure there's
any
> one
> good solution.
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
