2025/04/30

Newest at the top

2025-04-30 23:17:59 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-30 23:16:39 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 244 seconds)
2025-04-30 23:16:37 +0200tromp(~textual@2001:1c00:3487:1b00:81f6:6a75:5fad:c9b4) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-04-30 23:15:27 +0200DigitteknohippieDigit
2025-04-30 23:06:31 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-04-30 23:05:41 +0200michalz(~michalz@185.246.207.201) (Ping timeout: 265 seconds)
2025-04-30 23:00:25 +0200Digit(~user@69.47.7.51.dyn.plus.net) (Ping timeout: 244 seconds)
2025-04-30 22:59:57 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-30 22:59:42 +0200Digitteknohippie(~user@69.47.7.51.dyn.plus.net)
2025-04-30 22:57:12 +0200bliminse(~bliminse@user/bliminse) (Quit: leaving)
2025-04-30 22:55:53 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-04-30 22:54:47 +0200DigitteknohippieDigit
2025-04-30 22:49:22 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds)
2025-04-30 22:44:09 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-30 22:42:52 +0200Digit(~user@69.47.7.51.dyn.plus.net) (Ping timeout: 276 seconds)
2025-04-30 22:41:40 +0200 <mauke> but that was too easy
2025-04-30 22:41:31 +0200Digitteknohippie(~user@69.47.7.51.dyn.plus.net)
2025-04-30 22:41:05 +0200 <mauke> in my case, I rewrote the interpreter in perl :-)
2025-04-30 22:41:02 +0200 <monochrom> heheh
2025-04-30 22:40:57 +0200 <mauke> hah
2025-04-30 22:40:43 +0200 <geekosaur> I think I used it exactly once. I could argue that it drove me to Haskell 🙂
2025-04-30 22:40:35 +0200 <mauke> but the man page described it wrong, so my code (carefully written against the documentation) didn't work and in the end I had to write my own lookup table from scratch
2025-04-30 22:39:18 +0200 <mauke> I remember hsearch specifically because I actually tried to use it once when I was writing my first interpreter
2025-04-30 22:37:48 +0200 <mauke> hsearch is not standard C, luckily
2025-04-30 22:35:44 +0200 <geekosaur> I woul;d say they'd be stupid to have standardized it, but I think they standardized the System III/V hashtable etc. crap…
2025-04-30 22:34:32 +0200 <mauke> if it's not ISO 9899, not at all :-)
2025-04-30 22:33:18 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2025-04-30 22:32:34 +0200 <geekosaur> dunno how standard you consider it, but gdbm maintained the ancient interface until a few years ago iirc
2025-04-30 22:31:57 +0200 <geekosaur> libdbm used to
2025-04-30 22:31:05 +0200 <mauke> I'm not sure if there's any standard C function that passes structs by value outside of div/ldiv
2025-04-30 22:29:59 +0200 <mauke> they definitely were there when C was standardized in the 1980s, but none of the older APIs use them
2025-04-30 22:29:14 +0200 <mauke> I don't remember if they were implemented by the time K&R was published
2025-04-30 22:28:59 +0200 <mauke> pass-by-value structs were not implemented in the very first C compiler
2025-04-30 22:28:22 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-30 22:26:43 +0200Buliarous(~gypsydang@46.232.210.139) Buliarous
2025-04-30 22:26:15 +0200Buliarou1(~gypsydang@46.232.210.139) (Remote host closed the connection)
2025-04-30 22:25:06 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-04-30 22:21:26 +0200j1n37(~j1n37@user/j1n37) (Read error: Connection reset by peer)
2025-04-30 22:20:08 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-04-30 22:18:52 +0200dolio(~dolio@130.44.140.168) dolio
2025-04-30 22:17:38 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds)
2025-04-30 22:17:36 +0200dolio(~dolio@130.44.140.168) (Quit: ZNC 1.9.1 - https://znc.in)
2025-04-30 22:17:04 +0200Square3(~Square@user/square) (Ping timeout: 245 seconds)
2025-04-30 22:16:54 +0200j1n37-(~j1n37@user/j1n37) (Read error: Connection reset by peer)
2025-04-30 22:16:35 +0200 <EvanR> link time optimization aside
2025-04-30 22:16:18 +0200 <EvanR> for externally visible callable things I would hope not
2025-04-30 22:14:12 +0200Square2(~Square4@user/square) Square
2025-04-30 22:13:12 +0200 <monochrom> Here is a question I would need to resolve first. Does the calling convention vary by optimization level?
2025-04-30 22:12:38 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-30 22:11:57 +0200dolio(~dolio@130.44.140.168) dolio