ctf: Use g_time_val_from_iso8601 instead of g_date_time_new_from_iso8601
authorSimon Marchi <simon.marchi@efficios.com>
Thu, 2 May 2019 20:53:30 +0000 (16:53 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Fri, 3 May 2019 22:19:40 +0000 (18:19 -0400)
commitcca91513321176e147e04c9d1457a34044f244f0
tree1478b78fb25bfca8d90c380c2489a671f0da1feb
parent8e0dec5af1525f180587969362bfbd95483151bd
ctf: Use g_time_val_from_iso8601 instead of g_date_time_new_from_iso8601

g_date_time_new_from_iso8601 was introduced in glib 2.56, which is quite
recent.  To support build with older glibs, change the code to use
g_time_val_from_iso8601 instead, introduced in glib 2.12.

The code in question only uses this function to validate that the passed
string is ISO8601-compliant, it doesn't use the resulting time value.

The problem of g_time_val_from_iso8601 is that its result is not year
2038-safe on 32-bit systems.  We can expect that by then, that function
will have been removed from glib, forcing us to update our code.

Change-Id: I2f4fdfce9020ecefcfb5d653a3885d343e49bd76
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/1245
Reviewed-by: Michael Jeanson <mjeanson@efficios.com>
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
plugins/ctf/fs-sink/fs-sink-trace.c
This page took 0.024739 seconds and 4 git commands to generate.