overloading with the same parameter-set ? - page 2

New comment
 
Abejorro:

Yes, I also declared arrays as public and that's it. But all the security, checks and validating and so on has to be involved and tested every time again on the side. With the OOP-design I can cover all that in a smart class and forget. And with this realization here the update in code could be done only with a new declaration. (developers spend always hours and days to prevent 30 min of boring work ;-)

Thanks for the link. It is close to my wishes. Sadly the const didn't make any difference here. But I have to look a little deeper...

I agree with reasons you mentioned, but you still can implement the usual setter and getter methods for the OOP encapsulation. The specific problem is with overloading the operator.
 
Abejorro: We can start with that part in which I'm not looking for a pointer to data !
You already rejected an array of objects.
Abejorro: An array with objects would be horrible
12
New comment