lemmysmash
- 0 Posts
- 6 Comments
Joined 4 months ago
Cake day: February 26th, 2026
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
lemmysmash@piefed.socialto
Technology@lemmy.world•Let us filter AI slop, you cowards - Online platforms could prove whether AI labels work by giving us a filter option, but then they’d have to face reality.English
5·5 days agoHa, peasant! They’re not here to give you options, they’re here to make you watch more of the stupid garbage and click on more ads.
lemmysmash@piefed.socialto
Green Energy@slrpnk.net•TIL the cost of transporting energy aroundEnglish
2·7 days agoWhat about Uranium? How expensive is that?
lemmysmash@piefed.socialto
LocalLLaMA@sh.itjust.works•Gemma4 12b released with "unified" approach to multi-modalityEnglish
3·7 days agoAre there already any uncesored models based on it? Asking for a friend…
lemmysmash@piefed.socialto
C Programming Language@programming.dev•Is this a limitation of scanf() or bad control flow?English
6·11 days agoI’m too lazy to confirm, but I think scanf (as well as many other I/O functions) works on top of the buffered input. I.e. when you scanned only one character on the first run of scanf but there are more left in the buffer, then subsequent calls will read from that buffer, e.g.
printf("your prompt>") /* you type 123 */ /* buffer contains: "123" */ scanf(...) /* you scanned 1 char ("1") */ /* buffer contains: "23" */ printf("new prompt>"); /* the prompt has been printed AFTER your previous input but the buffer hasn't been reset! */ /* buffer contains: "23" */ /* you type 456 */ /* buffer contains: "23456" */ scanf(...) /* scanf returns "2" */ /* buffer contains: "3456" */In general you have two options:
- drain the buffer after / before each loop cycle
- use unbuffered I/O
For both cases, do your research on how to do it :) That K&R from above should be a great start indeed.


You are absolutely right to question that! Let me check…