Use pull processing when compiling a scenario

[GoogleCodeExporter]

For now, the code that compiles a scenario is a mix of pull and push 
processing. The SUT is first compiled (push), then the rest of the instructions 
in the scenario are compiled (pull).

So the SUT appear always first in the compiled stylesheet or query.  This is 
wrong.  For instance a variable can appear before the SUT, and must be in 
scope in the compiled stylesheet or query.

Solution: refactor the scenario compilation to use pull model throughout.

Original issue reported on code.google.com by fgeorges on 28 Feb 2010 at 11:11

• Blocking: #7

[GoogleCodeExporter]

Actually, to solve this variable-before-SUT issue, I think we instead have to 
use 
grouping (everything up to the SUT, then everything else), as the first group 
has to be 
embed into its own template element.

Original comment by fgeorges on 13 Mar 2010 at 4:59

[GoogleCodeExporter]

Original comment by fgeorges on 15 Sep 2010 at 7:23

• Added labels: Milestone-Release0.4

[GoogleCodeExporter]

Original comment by fgeorges on 11 Sep 2011 at 6:27

• Added labels: Milestone-Release0.5