REPLY: 2:221/1.58@fidonet 286d3cf1
MSGID: 2:280/464.113 6967d63f
CHRS: UTF-8 4
Hej August!

> that means you are building that source using 2017 C standard gcc
> support not the 2023 C standard based gcc default....

Exactly.

> That may mean that gcc developers are getting sloppy,

No it doesn't.  Without overthinking this, it means that the binkd source
isn't quite up to speed as far as c standards are concerned and that gcc
provides backwards compatibilty via the -std switch.

> there is an inherent code issue that they are tripping over.

No.  It compiles fine by using older c standards without having to revert to
an older gcc release.  If anything it is the binkd maintainer(s) who are
behind the times.  On the plus side it is a very easy fix and as luck would
have it gnu17 can produce a vastly more capable strftime than gnu99,
especially with regards to rfc-3339 formatted output such as below;

:read !date --rfc-3339=ns
2026-01-14 18:04:01.153826413+00:00

Overkill for sure but the nanosecond part could be used to ensure uniqueness
in a multiuser enviroment.

Het leven is goed,
Maurice

-o  -o  -o   o- -o   o-  o-  o-  o-  o-  o- -o   o- -o  -o  -o
 (\  (\  (\ /)   (\ /)  /)  /)  /)  /)  /)   (\ /)   (\  (\  (\
 ^^  ^^  ^^ ^^   ^^ ^^  ^^  ^^  ^^  ^^  ^^   ^^ ^^   ^^  ^^  ^^
... Is... glisnaþ glæshluttur, gimmum gelicust, flor forste geworuht.
    Ice glistens glass-clear, gem-like, a floor built by frost.
--- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
 * Origin: Little Mikey's EuroPoint @ (2:280/464.113)
SEEN-BY: 10/0 1 103/705 105/81 106/201 124/5016 128/187 129/14 153/757
SEEN-BY: 153/7715 154/10 30 110 203/0 214/22 218/0 1 601 700 840 860
SEEN-BY: 218/880 221/0 226/30 227/114 229/110 112 134 206 300 317
SEEN-BY: 229/400 426 428 470 664 700 705 240/1120 5832 263/1 266/512
SEEN-BY: 280/464 5003 291/111 292/8125 301/1 310/31 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 460/58 633/280 712/848 770/1 902/26
SEEN-BY: 5020/400 5075/35
PATH: 280/464 103/705 218/700 229/426