Quoting Rickard Öberg <[email protected]>:
On 2010-01-18 14.36, Stanislav Muhametsin wrote:
where @Optional refers to return-value (as it doesn't make sense to
say "Optional" on the method), and @Assigned is clearly for the
method, and yet the implementation AssignedConstraint simply
implements Constraint<Assigned,Assignable>.
Would that could cause any ambiguity in case return-value constraint
takes some parameters too?
Such as...?
For human reader I meant, in case there is some constraint named so
that it can be thought to be applied to both return value and
invocation handling. In those cases it would be required to manually
go and check the definition of tagging interface. A small labour in my
opinion, someone else might disagree though. :)
However, otherwise your syntax idea makes good sense. Oh, and I don't
think it was specified at which time return-value and
method-constraints are being invoked. Right after concerns, but before
mixin implementation?
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
