Michael Hoffer

Whenever you create a valid control-flow, VRL will automatically create an equivalent groovy class in the background. To accomplish that, it turns the visual control flow into code, the code...

Thanks for letting us know. I still prefer my own build since it is sometimes necessary to choose a very specific occt version only available as source package. Have you...

Thanks for your detailed response. I agree that the CMS paper lacks some important details. In general I think that the authors of such papers should provide plain implementations of...

I like the proposal. Being able to optionally specify the coordinates would satisfy most use cases without complex reader logic.

The current implementation only inserts one invocation into the loop. Chained or nested invocations are left outside of the loop.

To improve the current instrumentation implementation we should introduce a clean event api that can publish events to registered observers without changing the instrumented code. Therefore, we should add an...

Basic CSG instrumentation works!

another example:

Event generation for return statements has a bug (no event can be fired after returning from a method). **Example:** ``` java __vrl_reserved_intermediate_var_6); VRLInstrumentationUtil.__preEvent("14", "return", __vrl_reserved_intermediate_var_6); return __vrl_reserved_intermediate_var_6; VRLInstrumentationUtil.__postEvent("14", "return"); }...

Hmm, that is bad. For my use case modality cannot be optional. I use it for a fairly complex application (VRL-Studio) which crashes if I use JavaFX dialogs and violate...