Issue 1:
The subpixel precision of LSD was lost in the implicit conversion to Vec4i
Solved:
Line point coordinates are stored in cv::Vec4f
No type conversion needed from extremes to kl float fields

Issue 2:
The keyline point fields for original image were not being correctly filled
Solved:
The points in original image are computed through scaling (using scale factor and octave index)

Just adding a float cast (since a float is being assigned to)
allows MSVC to compile and should not affect other compilers.

Adding the decimal point means that VS doesn't complain about
lack of overrides for sqrt with integers.

vector.data() does not exist in MSVC<2012, so I changed it to
&vector.front() which has the same effect (pointer to the first
element in the vector).

standard

fixed the hamming distance function not to use 64-bit pop count. This should fix compile errors on Windows