4 ms·
> If a line of code doesn't look like a function call, it's not calling anything. Why is that important to you?
by creata 3y ago
> If a line of code doesn't look like a function call, it's not calling anything.
Why is that important to you?
- deely3 3y agoI did not touch C for 20y but its make code easy to read and understand. And helps debugging and error searching more easy task.
- flohofwoe 3y agoIt's important for reading other people's code. When I see a function call then I know that "anything" can happen inside that function, so I better investigate. For anything that's not a function call it is obvious what happens under the hood. In languages like C++ I potentially need to check every operator if it is overloaded, and find the place where that happens (I think I haven't seen any IDE support to help with 'resolving' overloaded operators, but maybe that has improved in the meantime).
- deleted 3y ago[deleted]
- c_crank 3y agoSome of the worst bugs I have experienced are ones where code is executing without it being clear where it is executing. The front end stack is the most awful about this, where at any given moment all kinds of things might happen without notice. A clear, sequential program can be stepped through and understood.