osmo_fsm and time_t

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Thu May 23 02:12:02 UTC 2019


On Sat, May 18, 2019 at 01:05:49PM +0200, Harald Welte wrote:
> Hi Neels,
> 
> in the following commit:
> 
> commit 89991fdb7c01fa42e323577b4026985e580763cf
> Author: Neels Hofmeyr <neels at hofmeyr.de>
> Date:   Mon Jan 28 19:06:53 2019 +0100
> 
> you introduce language about restricting the timeout to a signed 32bit value,
> as time_t is not well-defined on 32bit systems.
> 
> What I'm somehow missing is where we are using time_t in this context? Neither
> osmo_fsm code nor the underlying osmo_timer_list seems to be using time_t.

I think I was first considering to use time_t, but since that didn't provide a
fixed range in a cross-platform way, I chose int32_t instead. IIRC.

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20190523/c2c8660e/attachment.bin>


More information about the OpenBSC mailing list