Yes UB indeed, I just went with obfuscation mode. (-:

this is the same in the Python version, because this kata is a puzzle

fixed

description now states:

If an index is beyond the string, it should be ignored.

Yeah, I’m a pretty weird dude. I have an entire list of various sayings, quotes, and aphorisms from different people and languages. I'm pretty sure that particular one comes from a Latin book I have called Sententiae by Publilius Syrus. Most of the Latin ones I use are from him. He has a ton of good ones. You should check it out.

Yes, I’ve learned quite a few tricks from Code Golf on Stack Exchange. That said, I don’t post there like I do on Codewars. I just really enjoy trying to find the shortest C solution possible for each kata. It’s not just about code golf though, sometimes it’s about finding something equally as clever, like using shellcode tricks or inline assembly.

It feels like I’m always learning something new from someone’s unique solution. That’s really what I love about Codewars. But you’re totally right, I should visit Code Golf SE more often.

“Aliquid semper addiscendum est.”

On this song, it's like cheating.

On Baby shark lyrics generator, it's like PPE.

I thought it should be possible, but I didn't know and I didn't bother to find out that way to avoid using a temporary file. Neat.

I'm pretty sure that my code is shorter even with the include (54 characters), and if we ignore whitespace (71). However, you're right that without the K&R style (no return type) implicit conversion, it would make my code 77 characters compared to yours which was 75. So in a fair competition according to your standards and without all the silly tricks you are right your code would be the shortest. Ç'est la vie (: it's still fun playing around with the technicalities and seeing what is possible! :D

thanks! :D

fixed there

Should be fixed, please verify.

I have no time to fix this today, but if anyone gets to this before me, here is how to fix the issue: https://docs.codewars.com/languages/cpp/igloo/stringizers#stringification-with-stringizert

Yes, I’m learning so much more about the technical intricacies of C through golfing than I would normally, especially by studying everyone else's solutions. You and a handful of others consistently come up with the most creative, mind-blowing solutions that I never would have thought of, and I’ve learned so much from all of you.

Thanks! :D you too

I totally get it. Yeah, I've noticed you ignore spaces too, and that’s tripped me up a couple of times, lol. I’m just trying to find the most golfed solution by any means necessary. I was originally following the C23 standard as well, until I saw other solutions that didn’t follow it, and when I tried it, it worked. So I guess if Codewars allows it, then it’s fair game? But I totally agree. I wish they would enforce the most recent standard or let us sort solutions by the standard we prefer to use.

Aww man, I'm glad you commented because I totally forgot to credit Unamed for finding the Unicode chars. To be honest, the only thing I know is how to memset opcodes inside 16-byte double longs and I only learned that from asking Monadius. The smallest solution I've found is 10 bytes, though I've seen some of his solutions at just 8 bytes, so I really need to ask Monadius and Unamed how they pull this off. I'm honestly clueless about how you convert opcodes to Unicode chars. My goal here was just to find the shortest solution possible. Thanks anyways! Cheers! :D