> Shouldn't the exception be stored somewhere? E.g. in the result, the
> visitor, the evaluation environment or where ever. Just somewhere that I
> can access it after the evaluation has failed.

Yes. I've thought about this occasionally, but it's not that high on a
much too long list of problems. Please raise a Bugzilla, so that I can't
forget or dismiss it as one of my own ramblings.

It's not that easy:

a) OCL defines that there is exactly one invalid.
b) OCL definjes that a bad evaluation is invalid.
c) if an expression does ...oclIsInvalid() then invalid wasn't a problem.
d) EMF throws a variety of RuntimeExceptions

I'm inclined to ignore a) since the uniqueness of invalid isn't sensibly
observable, so an invalid-with-context should be feasible.

Am 08.10.2010 16:35, schrieb Ed Willink:
> Hi Eike
>
>> Shouldn't the exception be stored somewhere? E.g. in the result, the
>> visitor, the evaluation environment or where ever. Just somewhere that I
>> can access it after the evaluation has failed.
>
> Yes. I've thought about this occasionally, but it's not that high on a much too long list of problems. Please raise a Bugzilla, so that I can't forget or dismiss it as one of my own ramblings.
>
> It's not that easy:
>
> a) OCL defines that there is exactly one invalid.
> b) OCL definjes that a bad evaluation is invalid.
> c) if an expression does ...oclIsInvalid() then invalid wasn't a problem.
> d) EMF throws a variety of RuntimeExceptions
>
> I'm inclined to ignore a) since the uniqueness of invalid isn't sensibly observable, so an invalid-with-context should be feasible.
That'd be my favorite, too ;-)