2025/12/04

Newest at the top

2025-12-04 21:05:53 +0100Googulator15(~Googulato@2a01-036d-0106-479c-d9ec-010d-f188-ffcb.pool6.digikabel.hu)
2025-12-04 21:05:44 +0100Googulator15(~Googulato@2a01-036d-0106-479c-d9ec-010d-f188-ffcb.pool6.digikabel.hu) (Quit: Client closed)
2025-12-04 21:04:51 +0100lambda_gibbon(~lambda_gi@208.83.175.39)
2025-12-04 21:04:00 +0100pavonia(~user@user/siracusa) siracusa
2025-12-04 20:58:44 +0100bggd(~bgg@2a01:e0a:fd5:f510:9b09:80f:2f26:e3ad) (Quit: std::move)
2025-12-04 20:56:59 +0100peterbecich(~Thunderbi@172.222.148.214) peterbecich
2025-12-04 20:52:58 +0100Pixi(~Pixi@user/pixi) Pixi
2025-12-04 20:52:41 +0100Pixi(~Pixi@user/pixi) (Quit: Leaving)
2025-12-04 20:49:00 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-12-04 20:41:05 +0100TypesWithAHammergAy_Dragon
2025-12-04 20:40:22 +0100gAy_DragonTypesWithAHammer
2025-12-04 20:39:49 +0100lambda_gibbon(~lambda_gi@208.83.175.39) (Ping timeout: 246 seconds)
2025-12-04 20:36:37 +0100dhil(~dhil@5.151.29.139) (Quit: Leaving)
2025-12-04 20:34:55 +0100Square2(~Square4@user/square) (Ping timeout: 246 seconds)
2025-12-04 20:30:37 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 264 seconds)
2025-12-04 20:30:12 +0100 <EvanR> redacted
2025-12-04 20:30:02 +0100xnyhps(~xnyhps@s.xnyhps.nl) (Remote host closed the connection)
2025-12-04 20:28:33 +0100 <monochrom> haha
2025-12-04 20:27:56 +0100 <ski> rebased ?
2025-12-04 20:27:38 +0100 <tomsmeding> fortunately -- contrary to segfaultfizzbuzz's wishes -- history is being revised regularly :)
2025-12-04 20:27:18 +0100AlexZenon_2AlexZenon
2025-12-04 20:26:25 +0100 <tomsmeding> it seems that now is really the time that I've not used C for a long enough time that I forget basic syntax like this
2025-12-04 20:25:01 +0100 <int-e> . o O ( it's called "revising history", I learned today )
2025-12-04 20:21:05 +0100 <tomsmeding> :)
2025-12-04 20:21:00 +0100 <monochrom> Your brain makes sense, therefore you don't understand a poor syntax choice in C. :)
2025-12-04 20:20:51 +0100 <tomsmeding> (I had to pass -std=c99 -pedantic to get gcc to complain about it)
2025-12-04 20:20:38 +0100 <tomsmeding> 2. what is my brain doing
2025-12-04 20:20:33 +0100 <tomsmeding> 1. you're right
2025-12-04 20:20:19 +0100 <tomsmeding> or wait what
2025-12-04 20:20:15 +0100 <tomsmeding> TIL
2025-12-04 20:19:57 +0100 <monochrom> But C didn't have the o, you go straight to 0777
2025-12-04 20:19:15 +0100 <tomsmeding> I'd rather expect that all mentioned examples got 0o from C :p
2025-12-04 20:18:42 +0100 <tomsmeding> mauke: uh, what about C?
2025-12-04 20:16:55 +0100 <tomsmeding> got the language wrong, but at least it exists in a common language :p
2025-12-04 20:16:18 +0100 <tomsmeding> int-e: Swift seems to have ..< with the meaning I had in mind
2025-12-04 20:15:10 +0100 <tomsmeding> int-e: I could have _sworn_ rust had ..<
2025-12-04 20:11:47 +0100gehmehgehgmg
2025-12-04 20:08:21 +0100 <mauke> but the exponent is required
2025-12-04 20:08:15 +0100 <mauke> kind of. perl supports 0o0.4p0
2025-12-04 20:07:12 +0100ski. o O ( `0o0.4' )
2025-12-04 20:05:13 +0100 <int-e> But not Pike (which is another branch of LPC), so I think the caveat is important.
2025-12-04 20:03:40 +0100 <int-e> Rust too. The aforementioned LPC too (at least in its modern ldmud dialect).
2025-12-04 20:03:39 +0100 <c_wraith> actually, I guessed it based on the syntax provided in the binary literals extension rather than looking for a reference. at least things are consistent
2025-12-04 20:03:29 +0100 <mauke> nice
2025-12-04 20:02:03 +0100 <int-e> let's see.. Python 3 does it and forbids leading zeros in decimal literals on top of that
2025-12-04 19:59:02 +0100 <mauke> do any other programming languages (outside of Perl/Haskell) support 0o notation?
2025-12-04 19:57:46 +0100 <haskellbridge> <loonycyborg> Probably it's possible to write a function that will map on the element number in tuple that you specify as type level Natural :P
2025-12-04 19:57:36 +0100 <mauke> 0o (pronounced "uh-oh")
2025-12-04 19:56:35 +0100 <monochrom> heh
2025-12-04 19:56:19 +0100 <c_wraith> I found myself looking for how to write octal literals for the first time today. after almost 20 years using Haskell.