In this case I don't see a gain in making a class out of 1 function. You would gain more if for example you have a class for weeks and there are different actions that a developer can make that class have. For example a developer can make a week to be print out in different formats, to be added or substracted. Stuff like that.
I am not sure if I explained myself well, but there are various reasons to design classes and one of them is to encapsulate common actions (methods) applied to an object.
Donít see like it is object oriented vs procedural , just one brunch of programming flourished to something of its own. I have seen object oriented thinking in programs written before object oriented came out, in languages that where strict procedurals (like COBOL). The thing with your script is that it has many variables hard coded, and it is ok for now that you have only two functions but what are you going to do next time you want to modify something. You will always include this code and change the variables ?, more over tomorrow you will have more function in the same logic chapter , how will you group them ? Object oriented programming isnít just a trend, it is the best thing we have so far in logic encapsulation, but as a tool can be used in wrong ways too (I could say more on that but that would be out of topic)
"What are the advantages of using OOP over procedural?"
-OOP has features you can never use with procedural work. Magic methods (example : __get class function (method)is called every time you try to access a variable from object (attribute) that does not exist), so you can do all sorts of tricks with magic methods.
-You split your program in chunks all having their purpose.
-Less code, more functionality. Smart code, in general. In procedural you have to include or copy bunch of stuff over and over again.
-You change a class method, you change it in the whole program.
-I can continue on, but you just have to try it. :P
Take the following function, and if I were to make this into a class (which I have no idea how to yet!) what would I gain ?
-It's not so much in your particular piece of code that would change, your application structure would change, probably resulting in less code.
Let me put it simpler then:
You can write a whole app with 10 000 lines of tidy code, and the same app with less quality functionality with 90 000 lines of code of mess, too much includes, too much if statements, and too much code that needs to be "shut uff" for most pages.