SPeCS Research Group

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======= Legacy LARA =======

This section contains LARA constructs that are still valid, but for which newer (and recommended) alternatives exist.

==== Select ====

(Alternative: Query.search())

Select with full join point chain:

<code lara>
select program.file.function.body.loop end
</code>

Select with only last join point. The chain is induced, produces the same result as above:

<code lara>
select loop end
</code>

Assign the selected join points to a variable for later use:

<code lara>
LOOPS: select loop end
</code>

Assign an alias for specific join points:

<code lara>
select ($p=loop).($c=loop) end
</code>

==== Apply ====

(Alternative: for...of on return of Query.search() - i.e. weaver.Selector instances)

Apply after a select:

<code lara>
select loop end
apply
    println($loop.rank);
end
</code>

Apply on a previously selected set of join points:

<code lara>
apply to LOOPS
    println($loop.rank);
end
</code>

It is possible to perform a natural join on two sets of join points:

<code lara>
LOOP_START: 	select function.body.loop.($loop_start = first) end
FUNCTION_FIRST: select function.body.first end

apply to LOOP_START::FUNCTION_FIRST  
    // Init counters at the beginning of the function
    $first.insert before%{counter_[[$loop.uid]] = 0;}%;

    // Increment counters when entering the loop
    $loop_start.insert before%{counter_[[$loop.uid]] = counter_[[$loop.uid]] +1;}%;

    // ...
end
</code>

Use of join points with aliases inside the apply statement:

<code lara>
select ($p=loop).($c=loop) end
apply
   $p.exec Interchange($c);
end
</code>

==== Conditions ====

(Alternative: Query.search() filters)

Using a condition block:

<code lara>
select function end
apply
    // ...
end
condition
    $function.name == 'kernel'
end
</code>

Combining conditions using && (and) and || (or) operators:

<code lara>
select loop end
apply
    $loop.exec Unroll(2);
end
condition
    $loop.is_innermost &&
    $loop.type=="for"
end
</code>

Using "filter" conditions on the join point chain:

<code lara>
select function{name=='kernel'} end
apply
    // ...
end

// OR
select function{'kernel'} end // uses the default attribute of the join point
apply
    // ...
end
</code>


==== Automatic import of JS files ====

(Alternative: manually import JS files / use config option)

In previous versions, any JS file that appeared in include folders was automatically loaded and executed. During a period this behavior was disabled if the include folder had the name ''src-lara'', and now by default, is completely disabled.

JS files in include folders are no longer automatically loaded, they have to be either manually imported (see [[doc:lara:tips#importing_js_files|Importing JS Files]]), or the configuration option "Automatically import JS files in include folders" must be enabled.
SPeCS Research Group

User Tools

Site Tools

Page Tools
