Overloading

Posted Apr 27, 2014 17:20 UTC (Sun) by zorro (subscriber, #45643)
In reply to: Overloading by khim
Parent article: Porting the Go compiler to Go

Thus we have this “nice” library which is 1. Useless for interprogram communications because it's inefficient.

No, it is not inefficient.

2. Useless for human-to-program communication because it's not 18n-friendly.

Depends on who the human is. Many C++ programs communicate with developers and/or service engineers only (through log and configuration files). In my experience, support for a single language, typically English, is usually sufficient for these.

So… what's left? Logging and debug-only tracing

Yes, that's all. But that is sufficient for many applications where C++ is used for its strengths.

(one is advised not to use streams with in-prod tracing because if inefficiency).

Citation needed. In my experience, C++ streams are not more or less efficient than other mechanisms. And in all C++ programs I have been involved with, trace statements are implemented with macros so they have close to zero runtime overhead when not enabled.