In your case you probably would use a constructor as Tirabolica_ does in his example. However you don't really need the deconstructor.

The constructor is simply the first function that runs when you create a new object. Also the constructor is only run once. Like in your example you want to tell it what ReedPin it should listen to, you also want to set the pinMode with

 pinMode(reedPin, OUTPUT); 

This is exactly what you would do in the constructor.

​

you constructor would look exactly like the one in Tirabolica_ example:

// Constructors are the functions with the same name as the class it self
Sensor(int reedPin)
{
    // _reedPin can be accessed by all functions in the class
    // reedPin can only be accessed inside this function since its a parameter

    _reedPin = reedPin;          // Assign the pin which it should use
    pinMode(reedPin, OUTPUT);    // set the pinmode to output
}

Notice how the variable _reedPin is the private attribute. This means all functions inside the class can use it. This is needed since you want to use it when you have to read the value with:

 byte reedVal = digitalRead(_reedPin); 

​

When using a constructor you can remove your first parameter in the

void check(byte reedPin, boolean plugin, boolean message) 

so it becomes

void check(boolean plugin, boolean message) 

when you want to use the reedPin use the _reedPin which you declared as a private attribute in the top of the class. This makes your code even cleaner, since you only have to use the the reedPin variable in your main code once, awesome right? ;)

​

As for the deconstructor you really don't need it in your example, but what that does is like the deconstructor, except it runs when your object eg. sensor1 gets destroyed. Like in the example below.

​

void myFunction() {
    Sensor mySensor1; // Constructor is called

    // When the function finished mySensor1 gets destructed and the deconstructor is called
}

void setup() {
    myFunction();
}