# and #List functions date/timestamp encoding issue

[dansmith65]

The # and #List functions encode dates in a specific local's format. If you attempt to read the encoded data on a file/system with a different local setting, it may fail with EvaluationError code 500.

This value was encoded in a new file on a computer set to display dates as YYYY-MM-DD:

"$ts = GetAsTimestamp ( \"2016-02-02 6:48:01 PM\" ) ;¶"

If I download this file and open it on the same computer, I get this result:

#Get ( "$ts = GetAsTimestamp ( \"2016-02-02 6:48:01 PM\" ) ;¶" ; "ts" ) = "?"
and
EvaluationError ( #Get ( "$ts = GetAsTimestamp ( \"2016-02-02 6:48:01 PM\" ) ;¶" ; "ts" ) ) = 500

I don't think this issue can be reproduced within a single file, which is probably why our current test cases haven't discovered it.

[petrowsky]

Looks like you would need to have a file created from a different local
and store it within a container and run tests against that file if you
wanted to test it.

On 2 Feb 2016, at 18:00, Dan Smith wrote:

The # and #List functions encode dates in a specific local's format.
If you attempt to read the encoded data on a file/system with a
different local setting, it may fail with EvaluationError code 500.

This value was encoded in a new file on a computer set to display
dates as YYYY-MM-DD:

"$ts = GetAsTimestamp ( \"2016-02-02 6:48:01 PM\" ) ;¶"

If I download this
file
and open it on the same computer, I get this result:

#Get ( "$ts = GetAsTimestamp ( \"2016-02-02 6:48:01 PM\" ) ;¶" ; "ts" 
) = "?"
and
EvaluationError ( #Get ( "$ts = GetAsTimestamp ( \"2016-02-02 6:48:01 
PM\" ) ;¶" ; "ts" ) ) = 500

I don't think this issue can be reproduced within a single file, which
is probably why our current test cases haven't discovered it.

---

Reply to this email directly or view it on GitHub:
#32