The parameters were required for the recursion and are no longer necessary.

In the previous commit, I fixed the problem caused by having only one value in the interpolation table by return 0. On second thought, it makes more sense to assume a "constant interpolation" and return the one stored y-value for any x.

Replaced the linear search with a binary search and added unit tests.

The edge-cases of an interpolation are now clearly separated and checked in a uniform way.

Cleaned up the unit tests a bit so that it's easier to spot where errors are coming from.

A typo caused incorrect results for interpolated values at or beyond the
upper limit of the interpolation range. The unit tests were adjusted to
reflect this fix.

Rename Framework code directory to just that. Also delete Main and VS & Eclipse project file. Re #1881.

spotted my Russell, which by some C++ fluke appeared to, so far, to have done no harm.

re #1751 

Allow y-unit syntax for interpolation elements of IDF. Add this concept to Interpolation and testing this. 
Added additional user warnings in case users do not specify units recognisable by mantid
Updated result-units in HRPD_Parameters.xml.

Refs #1308
 

In Interpolation when outside table interpolate linearly instead of then taking endpoints.  
Refs #967.

<parameter name="somefunction:toplevel2" type="fitting"> 
  <lookuptable interpolation="linear" x-unit="TOF">
    <point x="1" y="1" />
    <point x="3" y="100" />
    <point x="5" y="1120" />
    <point x="10" y="1140" />    
  </lookuptable>
</parameter> 

Refs #967.

Added working Nexus test in IkedaCarpenterTest (possible now that workspace parameter map is loaded at the end of LoadInstrument).
Refs #967.