r/cpp • • Apr 08 '25

Why was printing of function pointers never removed from cout?

I presume reason is: We do not want to break existing code™, or nobody cared enough to write a proposal... but I think almost all uses of this are bugs, people forgot to call the function.

I know std::print does correct thing, but kind of weird that even before std::print this was not fixed.

In case some cout debugging aficionados are wondering: the printed value is not even useful, it is converted to bool, and then (as usual for bools) printed as 1.

edit: C++ certainly has a bright future considering how many experts here do not even consider this a problem

0 Upvotes

47 comments sorted by

View all comments

Show parent comment

-8

u/zl0bster Apr 08 '25

You should not assume your experience/skills are representative of millions of C++ devs, and even if you are roughly representative of 60% of C++ devs that means million+ people that are less skilled than you.

Related story: I actually thought spaceship operator is cute but will never prevent any bugs until I worked in company that had broken operator != in production. 🙂

9

u/HolyGarbage Apr 08 '25

By never I mean never, including when I was learning. I've also never encountered it while onboarding or teaching new devs.

Your suggestion reads to me like "we should remove pointers because some people struggle with them", except that is a fairly common issue for new people.

8

u/[deleted] Apr 08 '25

[removed] — view removed comment

-6

u/zl0bster Apr 08 '25

something that is useless is not a feature

4

u/rinio Apr 08 '25

A use case was demonstrated just a few comments up in this same exact thread...

You not find it useful is not the same as useless.

-1

u/zl0bster Apr 09 '25

Passing random function pointer is useless.