3 ms·

This might be your experiences, but I've never worked with people who called member functions methods in C++. I've seen C# programmers who had never worked with

This might be your experiences, but I've never worked with people who called member functions methods in C++. I've seen C# programmers who had never worked with C++ call them that, but in the C++ teams I can't recall an instance of that, even for multi lingual engineers Though I do tend to work with teams where the average age is higher than the industry average, that might be warping my anecdotal experiences I have had situations where the distinction matters, and they aren't academic either, but in API design, especially for libraries

stouset 2y ago
I’ve had a similar experience, but if someone called a method a function or vice versa, it’s never been unclear what they meant. And it’s never been something that people would have felt the need to correct someone on. I am aware of the distinction and I (probably?) instinctively use the two terms “correctly” the majority of the time. But if I just picked one or the other and used that word 100% of the time I would wager there would be zero confusion, except amongst pedants. For what it’s worth, I say this as an avowed pedant.