| 21 Jan 2025 |
 kapendev | Rust
My day is ruined. | 16:11:57 |
 fabric.input_output | skill issue | 18:09:11 |
|  yummy_licorice changed their profile picture. | 19:44:42 |
 nimble install python.zig? | 
Download 2025-01-21-155506_726x284_scrot.png | 20:55:14 |
| nimble install python.zig? | really happy with how this turned out, way better than having to memorize api call ids | 20:55:47 |
| nimble install python.zig? | * really happy with how this turned out, way better than having to memorize api call ids and return types | 20:56:27 |
| nimble install python.zig? | 
Download 2025-01-21-155644_855x250_scrot.png | 20:56:45 |
| nimble install python.zig? | thats the before | 20:56:54 |
 Elegantbeef | Really should wrap that onDone with proxy procedure so you don't need to specify {.stdcall.} | 20:56:54 |
| nimble install python.zig? | yea ive been meaning to do that just lazy, its problaby not even nessessary anymore bc I bypass the builtin callbacks and just use manual dispatch | 20:57:38 |
| nimble install python.zig? | the most important part is that its all auto generated now 🎉 never need to worry about updating the dll breaking version identifier stuff | 20:59:31 |
| nimble install python.zig? | * the most important part is that its all auto generated now 🎉 never need to worry about updating the dll breaking version identifier stuff ever again | 20:59:40 |
| 22 Jan 2025 |
| nimble install python.zig? changed their display name from @@prestosilver to nimble install python.zig?. | 00:28:09 |
|  zancodm. joined the room. | 00:55:47 |
|  clifzz joined the room. | 01:07:39 |
|  luckyhits_ joined the room. | 03:37:26 |
 anuke | What does the stdcall convention imply? | 05:08:46 |
| anuke changed their profile picture. | 05:08:48 |
| Elegantbeef | It uses the windows only stdcall convention | 05:15:09 |
| Elegantbeef | Only really need it for windows functions | 05:15:29 |
| Elegantbeef | https://learn.microsoft.com/en-us/cpp/cpp/stdcall?view=msvc-170 | 05:16:05 |
 demotomohiro | https://en.wikipedia.org/wiki/X86_calling_conventions | 05:19:21 |
|  smarterandsmarter joined the room. | 05:22:34 |
| demotomohiro | https://en.wikipedia.org/wiki/X86_calling_conventions#Microsoft_x64_calling_convention
When compiling for the x64 architecture in a Windows context (whether using Microsoft or non-Microsoft tools), stdcall, thiscall, cdecl, and fastcall all resolve to using this convention.
https://gcc.gnu.org/onlinedocs/gcc/x86-Function-Attributes.html
It seems cdecl, fastcall, thiscall and stdcall are x86-32 specific.
On x86-64 windows and UEFI, they become Microsoft x64 calling convention.
On other OS on x86-64, they become System V AMD64 ABI. | 05:35:37 |
| demotomohiro | So on x86-32 windows, your program probably crashes if you use wrong calling convention to call C functions.
But if you recompile it on x86-64 OS, it probably works as different name calling conventions are actually the same. | 05:41:39 |
|  m1l0js_20119 joined the room. | 06:57:57 |
|  britannia.zeta joined the room. | 15:17:37 |
| 23 Jan 2025 |
|  that_dude. changed their profile picture. | 03:21:14 |
|  @vigue:matrix.org joined the room. | 05:33:03 |
|  monkey085395 changed their profile picture. | 05:54:23 |
