[mdt-ocl.dev] stdlib origins

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi Alex

I think that the two variants are largely historical, but the Java 
version acts as a backup if the
model load fails.

This can be quite unpleasant standalone, because there may be two 
different stdlib models
if the EMF Registry package registration is performed too late. JUnit 
tests go bananas,
hence my submission of an OCL.initialize support.

   Regards

      Ed Willink

Alexander Igdalov wrote:
> Hi All,
>
> Before evolving this idea I would like someone to explain me why there are
> two ways of building the standard library:
> 1) using an ecore/uml model (oclstdlib.ecore and oclstdlib.uml)
> 2) by hand in OCLStandardLibraryImpl.build()
>
> Cheers,
> - Alex