tester("pneumonoultramicroscopicsilicovolcanoconiosis", "sisoinoconaclovociliscipocsorcimartluonomuenp");

Merged.

Fixed spelling mistake in C translation.

I think you do not need len. It is a dice so the number of faces is always 6. Unless you are considering a dice for dungeons and dragons.

Yea, I should've chosen a better name. Thanks :D

love it, just the name of prod is a bit misleading, took me a bit to realize what you wanted to do
its actually a denominator of the quotient, so when i(sum-i) is maximum, q is minimum
nice :)

once again, dont make it look good- make it look intimidating... :)

umm really?????

I just ported their code to C. I didn't add any extra features to detect foul play.

u really wanna do this? i dont even know c that much, just the basics :(

Would you mind your language a bit.

I agree with you. I was writting a more thoughtful response to your reply, and I just decided to delete it since it would wrap around to say, "I agree with you". I like your insight, though. It would be nice to have more conversations like this with you ;)

see also: A tale of two libcs

The author understands C well enough, I think. Some associated Internet drama is unfortunate.

I didn't follow Terry at all, but some of his archived videos contained some pretty agreeable philosophical positions. Neither do I follow John Carmack but I rather like this line:

If you're willing to restrict the flexibility of your approach, you can almost always do something better.

IMO strictly idiomatic, garden-variety, very verbose C often found on Codewars is just another kind of premature optimization: optimizing for "maintenance"... and aggressively promoting bloat. As opposed to the classic sense, when you don't already know where your code spends the most time, optimizing for refactoring is always premature because you never know what will need to change if the requirements change. This is just my relatively recent conclusion. Sure, people also optimize for readability, but I think that's mostly for the basic assumptions of maintenance & the current 'industry' status quo... which is broken anyway.

To be fair and honest, a lot of my solutions are what you said, tangled messes of expressions, usually just so I can avoid using curly braces as often as possible and try for minimal LOC. Sometimes things get ugly.

Also, to be fair and honest, I never studied / compared the assembly output, and I should.

I'm sorry, when I asked about 'others' I meant other collections of hacks or snippets with links that you could share. No, I don't know lots of these things, and I've only ever needed 2 or 3 of the hacks in that collection.

That double move is pretty sick. Someone may have had nightmares...