Case of double and float primitive types is not handled

[prakharporwal]

• Object Value is recorded in the binary files.
• This happens when value is stored in long value instead of a double.

Possible reason

• recordEvent for the Primitive double and float is recording wrong value .
• while reading if something similar to double.longBitsToDouble() can be called on primitive type.
• Similarly for float, this leads to int value instead of float.

eg. Actual : double a = 4614455732198220759L

Expected : a = 3.23d

using Double.longBitsToDouble() while writing into serialised value can fix this;

[takashi-ishio]

Thank you for the information. While the logger correctly translates primitive double/float values into long values during writing, Event.toString() did not decode the values into the original double/float values. As a result, you saw long values (e.g. 4614455732198220759L) in the textual output from LogPrinter.

To solve the issue, I have fixed Event.toString().

If you are directly manipulating Event objects in your program, please check the return value of getValueDesc() and call getFloatValue() or getDoubleValue() as the Event.toString() method does.