Property or method

Erik Porter is reviewing the ADO.NET for a book he is writing. He questions why HasChanges is a method and not a property. Erik implies that methods change states of an object in a complex way, but properties only change it a little.

In a comment, Paul Laudeman thinks the decision rides on the complexity of the code.

I like how Microsoft describes properties vs. methods in the MSDN library.

  1. #1 by HumanCompiler on August 11, 2003 - 4:33 am

    Thanks for the link to MSDN…good read! 🙂


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: