re: Static classes are evil VIEW POST

re: I think that's what I'm saying, by describing it as a pseudo-namespace. But what's your point? Because it sounds like you're trying to build an a...

My point is that static classes should not be used in OOP.

That example with decorated Strings is an OOP alternative to procedural StringUtils class.

It's okay to call functions though, like how your string example calls strtoupper and several others - but it's not okay to write/call your own functions?

I understand it's "not OOP", but "should not be used"?

I think there are well founded reasons why most languages support both paradigms - there are cases for functions and cases for classes, I think, and your string example is sufficiently complex and verbose as to leave me pretty firmly convinced of that.

Code of Conduct Report abuse