A is a function from the parameters of the engine, and the result to a boolean.
A is a function from the parameters of the engine, and the result to a boolean. It checks that some property is true
In order to call an A in the building code, when we don't know anything about the arity, we create a closure holding the parameters and reusltand pass the A function to it
In order to call an A in the building code, when we don't know anything about the arity, we create a closure holding the parameters and reusltand pass the A function to it
B is a function from the parameters of the engine to a boolean.
B is a function from the parameters of the engine to a boolean. It is effectively in calculating which scenario is to be used
In order to call a B in the building code, when we don't know anything about the arity, we create a closure holding the parameters and pass the B function to it
In order to call a B in the building code, when we don't know anything about the arity, we create a closure holding the parameters and pass the B function to it
this is a function from the parameters to Unit e,g, (P1,P2,P3)=> Unit
this is a function from the parameters to Unit e,g, (P1,P2,P3)=> Unit
This is just a type synonym to save messy code
This is just a type synonym to save messy code
turns parameters into fragment results.
turns parameters into fragment results. For example in XML in an engine 2 it might be (P1,P2)=>NodeSeq. I would love to know how to make this more type safe...
PF is a partial function from the parameters of the engine to a result R
PF is a partial function from the parameters of the engine to a result R
turns the params into a Fragment.
turns the params into a Fragment. This can be modified by the fragment specifiers
RFn is a function from the parameters of the engine to a result R.
RFn is a function from the parameters of the engine to a result R. It is used to calculate the result of the engine
In order to call a RFN in the building code, when we don't know anything about the arity, we create a closure holding the parameters and pass the B function to it
In order to call a RFN in the building code, when we don't know anything about the arity, we create a closure holding the parameters and pass the B function to it
This holds the data that the scenario builder is building.
this code is here for a truely hideous Eclipse interop bug that I wasn't able to duplicate in a test :( Basically if you have two tests with the same name, and one passes and one failes, then the Eclipse JUnit plugin I was using didn't work well
this code is here for a truely hideous Eclipse interop bug that I wasn't able to duplicate in a test :( Basically if you have two tests with the same name, and one passes and one failes, then the Eclipse JUnit plugin I was using didn't work well