Coding Horror: Properties vs. Public Variables

Why waste everyone's time with a bunch of meaningless just-in-case wrapper code? Start with the simplest thing that works-- a public variable. You can always refactor this later into a property if it turns out additional work needs to be done when the name value is set. If you truly need a property, then use a property. Otherwise, KISS! Update: As many commenters have pointed out, there are valid reasons to make a trivial property, exactly as depicted above:

* Reflection works differently on variables vs. properties, so if you rely on reflection, it's easier to use all properties.

* You can't databind against a variable.

* Changing a variable to a property is a breaking change.

Source: Coding Horror: Properties vs. Public Variables

So this answers the question on why you use properties in .NET and not just public variables.

I've always used properties but on occasion of used public variables. Small object, needed it quick so didn't bother with the getter or setters.

I work with a Java developer who abhors getters and setters, says it is Microsoft's way of disguising method calls. I disagree since I don't think the overhead involved is that great.

As far as creating the getters and setters, hey, that is what code snippets is for.

Comments

C# Spirograph Point Generators

Spirograph's are cool. See here and here . I put together three ways to generate points for a Spirograph, first using a Brute Force straight generate the points, second using a Parallel.For and third using LINQ.

FileSystemWatcher With the BlockingCollection

While working with the FileSystemWatcher I found that if too many files were created the built in buffer will overflowed and files will be skipped. After much research I found out about the Producer-Consumer Problem . Then I found that .Net 4 has the BlockingCollection which helps solve the issue. But how to use it with the FileSystemWatcher? On StackOverflow I found Making PLINQ and BlockingCollection work together . I'm not so interested in the PLINQ issue but this is a great example of using The BlockingCollection with FileSystemWatcher. [csharp] using System; using System.Collections.Concurrent; using System.Collections.Generic; using System.IO; using System.Linq; using System.Threading; namespace ConsoleApplication4 { public class Program { private const string Folder = "C:\\Temp\\InputData"; static void Main(string[] args) { var cts = new CancellationTokenSource(); foreach (var obj in Input(cts.Token))

Remote Controlled RoboTank

This is my version of the ever popular to build RoboTank. It uses an Arduino Mega 2560 with the AdaFruit motor shield and an XBee S1 to communicate to the DFRobot Gamepad. The sketch for the RoboTank makes use of the AFMotor.h to drive the motors and includes a serial parser to read and process the commands coming from the Gamepad. Robotank-Sketch.zip DFRobot Wireless Joystick

TechShorts

Search This Blog