code logs -> 2023 -> Thu, 22 Jun 2023< code.20230621.log - code.20230623.log >
--- Log opened Thu Jun 22 00:00:36 2023
00:36 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
00:52
<&[R]>
https://github.com/TodePond/DreamBerd perfect programming language
04:34
<@macdjord>
[R]: ... the horrror.
04:39 Degi [Degi@Nightstar-tgc378.pool.telefonica.de] has quit [Ping timeout: 121 seconds]
04:41 Degi [Degi@Nightstar-n0134q.pool.telefonica.de] has joined #code
06:03
<&McMartin>
One nice thing about relying on system popup boxes for stuff is that I get to actually label things FLAGRANT SYSTEM ERROR and nobody can stop me
06:04
<&McMartin>
Fun fact: the constant constants, constant variables, variable constants, and variable variables have direct analogs in C, and I would be unsurprised to learn that C# has them in there too
06:04
<@celticminstrel>
FLAGRANT SYSTEM ERROR
06:05
<&McMartin>
Computer over.
06:05
<&McMartin>
Error = very yes.
06:27
< Alek>
const const const
06:28
< Alek>
wat
06:46
<&McMartin>
I must assume that this was added after someone pointed out that the four-way variation he described was actually useful and arguably more sensible than the C-like syntax for it
06:47
<&McMartin>
(const char * is the "variable constant", and char * const is the "constant variable", and if you want an actual constant constant it's "const char * const" which nobody does)
06:48
<@celticminstrel>
I guess I'm nobody.
07:26
<&McMartin>
I don't think it's controversial to say that this is extremely rare to see in published code
11:20
< abudhabi>
What does that do? Make a pointer that can't be reassigned and whatever it's pointing at can't be modified?
13:51 gnolam [lenin@Nightstar-fkirhg.priv.bahnhof.se] has quit [[NS] Quit: Midsummer!]
14:04
<@celticminstrel>
Yeah.
14:52 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
14:52 mode/#code [+qo Vornicus Vornicus] by ChanServ
15:32 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
18:09
< abudhabi>
I hate copyright.
18:10
< abudhabi>
Bought a new laptop, and thanks to - apparently - HDCP, I can't use my DVI monitor with it as it is.
18:57 Kindamoody [Kindamoody@Nightstar-pqh9gl.tbcn.telia.com] has quit [Ping timeout: 121 seconds]
19:00 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code
19:02
< abudhabi>
Hm. I think I can get around this with an adapter.
19:03
< abudhabi>
I have a different laptop that works with my setup, via a HDMI to USB-C adapter.
19:04
< abudhabi>
The new laptop might work with a similar approach. It doesn't have USB-C, but it does have USB.
19:39 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
19:40 Kimo|autojoin [Kindamoody@Nightstar-pqh9gl.tbcn.telia.com] has joined #code
19:40 mode/#code [+o Kimo|autojoin] by ChanServ
19:42
< abudhabi>
Regrettably I don't appear to have the correct adapter.
20:06 Kimo|autojoin is now known as Kindamoody
21:35 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code
21:45 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
21:45 mode/#code [+qo Vornicus Vornicus] by ChanServ
22:09 murdock [murdock@Nightstar-q9o5sg.inf.spectrum.com] has joined #code
22:33 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
--- Log closed Fri Jun 23 00:00:38 2023
code logs -> 2023 -> Thu, 22 Jun 2023< code.20230621.log - code.20230623.log >

[ Latest log file ]