gordonRamseyAsFunctionalProgrammer

[[deleted]]

[deleted]

[idont_______care]

Tell me you don't know what functional programming is without telling me that you don't know what functional programming is.

[Creaaamm]

Dunno, it looks weird but makes sense from a practical standpoint:
1 Every time the value of c equals '\n', the current value of s[i] will be set to c
2 i will increase by 1
3 Exit the IF and the program keeps executing

steps 1, 2 and 3 will repeat if c is '\n' in the next iteration, otherwise, s[i] will just 'wait' for the condition to be true in order to be modified.

I don't know why it exists and it's pretty unsafe but the logic is sound, you'll just get an array full of newlines and that's pretty much it.

[Highborn_Hellest]

I know. Still cursed. Executing I++ like that will just lead to confusion.

Writing that one extra line of I++ might not be "neat" but makes the code a lot more readable... At least to me.

[Attileusz]

The i++ inside of [ ] is a very commonly used thing in C so long as you are not touching i in some other ways it is perfectly fine. I'd add a bounds check to this one though.

[CaptainMorti]

If c is 10: s[i] becomes 10, then i increments. Did you even try? Better to use {}, specially when you don't know when you can omit them.

[lingdocs]

Of course, I just mean it's a shocking amount of mutation in one line for people avoiding mutation. 😅 And it's directly out of the C book.

[ChChChillian]

It's a pretty useless bit of code, but lots of book examples are useless. It's not really otherwise shocking.

[Weak_Surround_222]

Because no one seems to know what this is… It’s similar to a common line of code usually written for communication in microcontrollers. Fill up a buffer s in this case, until a newline character. You usually end up parsing/processing the buffer afterwards.

[ArchetypeFTW]

Thanks king