Jump to content
Xtreme .Net Talk

Recommended Posts

  • Administrators
Posted

I take it you mean the idea of exposing variables as public rather than using properties...

 

The problem with public variables is the fact they can be modified from anywhere in the application with no restriction or validation whatsoever. If you declare the field as a property then you could perform validation in the set part to ensure any values assigned are valid or simply omit the set entirely to make the property read only and only allow changes through appropriate public methods. This effectively gives you more control over where changes to these variables can be made, allowing you to implement and validation or associated logic in one single place rather than multiple times throughout an application.

Posting Guidelines FAQ Post Formatting

 

Intellectuals solve problems; geniuses prevent them.

-- Albert Einstein

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...