Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the example of the OOP concept ‘Message Passing’ in C# (calling methods/Passing parameters/Firing Events/Handling Events/???) and why is it called message passing?
Method calls.
It’s called message passing to distinguish it from the imperative notion of “calling a function”, and to reinforce the idea that the receiving object decides what to do. On the call site, you just tell the receiver the “message”.
An example would be methods that are abstract in a class, and implemented in subclasses; or implementations of an interface method. When you call e.g.
GetEnumerator()through a variable of typeIEnumerable, you don’t know at the call site what code should actually be executed.