Now I am making a simulation program based on "C" language (still not "C++").

After knowing "Object-oriented programming", more than twenty years, through eternity time, has passed. I re-think again that,

"I wonder if the concept of object-oriented is really needed."

-----

- Readability is very bad. (Why should I feel hard to track my source codes?)

- An interface is not unique, so I cannot specify which method I should read.

- If the definition of an n object is in another file, code tracking is terrible complicated.

- If someone made an inherited object, I feel fear to make the method because I don't estimate results.

Of course, I know it is very convenience in order to make like a "rice-ball of data", though,

I think that "struct" is enough.

Do we really need a method to change the "rice-ball of data" with "rice-square of data”?

I think external functions are good to do the processes if we need them,

-----

I know better that this logic is unfair.

In my case, I have no plans to develop a system with someone in the future. The simulation program is just mine, so I will define the interface as my favorite.

It is freedom.

- I am going to use global variables,

- write numeric in source code directly, and,

- reuse the "GOTO" that is hated as a caterpillar, in the near future.

-----

However I am going to open my entire program I make as a hobby, the goody-goody feeling that

"I want to make the program codes open for someone's help."

is not a trace.

If you want to do additional test of my simulator, you should be working on in its own way of preparedness.