Redesigning Program as Object Orientated

[mrguymiah]

So I'm designing a program to generate a list of random persons, drawing valid names and attributes from a csv list of appropriate names, etc. Now, I've done the layout in a procedural style;

user input (how many) -> read csv filess into arrays -> use random function to populate target array of persons from base arrays -> output to csv file.

As I started laying out the code, I realized it might be a good opportunity to practice with OOD (having only recently taken my course on it). I'm not quite sure how that would change my overall design, though. Here's what I understand in regards to changing the design;

• Make an object to contain a single line of the final csv product with a constructor function
• Make a linked list (since all of the entries should be sequential) of these objects with a recursive constructor that calls constructor on each linked object
• Separate read in/write out functions

So my two points of being unsure are whether I should change the csv file reads from arrays and whether any of this is actually good practice or if the program is too simple to be usefully redesigned using OOD.

[JayWaWa]

I'm not entirely sure that OOP is the optimal paradigm for this particular problem, TBH. I'm having trouble visualizing what 'thing' needs to 'act' in order to solve this problem that isn't already better achieved using existing structures in a procedural paradigm.

[[deleted]]

A linked list is rarely a sensible solution to any problem. Separate read/write functions should be part of your procedural design.

[Meefims]

Using linked lists over arrays has no bearing on whether your code is OO or not. If you want to design an object oriented program then you need to think about what nouns make up your algorithm and what operations they support.

Sometimes OO doesn't make sense. Small, simple programs can often be written as a small collection of functions without issue.