What is the easiest (or the most effective) way to debug complete ocl? I am now copying and pasting pieces of a Complete OCL file in the OCL console but it would be great if I could put breakpoints or at least print object values in the Console
The QVTo debugger is quite useful so if you can wrap your Complete OCL
in a QVTo transformation that might help.
QVTo has a log() function.
OCL has a toString() that Eclipse OCL extends to everything.
You can add custom Java functions to your meta-model that print things
in your favourite way.
I've just fixed a bug, not yet on master, that allows e.g. a derived
"label" attribute to redirect to "label()" that can be overridden with
per-Object text representation. (There was a bug in the dynamic
dispatch.) This then works really well if "label" is high enough in the
inheritance so that it is the EAttribute that EMF chooses as the default
Generalizing the QVTo debugger for the new Pivot-based OCL and for
extension to QVTc and QVTr is in my plans, but it doesn't help you now.
On 17/11/2012 19:02, Andrea Sindico wrote:
> What is the easiest (or the most effective) way to debug complete ocl?
> I am now copying and pasting pieces of a Complete OCL file in the OCL
> console but it would be great if I could put breakpoints or at least
> print object values in the Console
On 20/11/2012 19:51, Andrea Sindico wrote:
> Hi Ed,
> where may I find the latest source code?
> A tried at http://www.eclipse.org/modeling/mdt/downloads/?project=ocl
> downloading both the SDK and the Core SDK but I could not find any src
> file in there
> Also is there any doc about the source architecture? is it an Xtext