(check another language specification - e.g., Java - and see the kind of structure that is used)

(new language for Weaver Specification; explain syntax; 'functions' instead of 'attributes')

(change 'attribute' to 'function')

(recommended syntax: $jp.exec <action_name>. Could it be $jp.action <action_name> instead?)

There are several actions that are defined by default in the LARA language.

(only supports before/after, around/replace removed; granularity is statement level)

(granularity is node itself)

(recommended syntax: var a = new Aspect(); call a;)

(independent of weaver)

Should return: → executionTime → stdOut → stdErr → exitStatus

(Should return the same as 'cmd', additionally can define a report)

Parts of the language that have not been decided yet and are still under discussion

Currently LARA has no way to define when we do a 'select', if we want just the direct joinpoints under it (e.g., children) or all its descendants.

E.g., select body.loop end will recursively return all the loops inside the body, there is no simple way to select only the loops that are directly under the body (excluding nested loops).

It is not defined the order of consecutive calls to insert before/after. If we do:

select a end
  $a.insert before 'before_1';
  $a.insert after 'after_1';
  $a.insert before 'before_2';
  $a.insert after 'after_2';
end

Should it appear like this:

'before_2'
'before_1'
a
'after_1'
'after_2'

Or like this?

'before_1'
'before_2'
a
'after_2'
'after_1'