Saturday, October 10, 2020

Digest for comp.lang.c++@googlegroups.com - 1 update in 1 topic

"Öö Tiib" <ootiib@hot.ee>: Oct 10 10:34AM -0700

On Friday, 9 October 2020 09:22:33 UTC+3, Jorgen Grahn wrote:
> over printf. I can imagine sitting in a project in the future which
> uses both printf, ostream formatting, Boost.format (in several
> flavors) and this one. I don't look forward to that.
 
IMHO both the printf and ostream<< can be discarded as soon there is
something better. Both are made inefficient by localization support
on one hand but on the other hand that localization support
isn't anywhere close to sufficient to help with anything.
Boost.Format addresses some issues with it but looks nerdy and seems
slow. That std::print also seems to address those issues plus have
less nerdy variants but I haven't measured its performance.
 
What remains missing in C++ is compile-time encoded/decoded textual
input/output that is useful for text-based protocols. Something
that does something useful like supporting escaping and de-escaping
special characters by some compile time fixed table but is not paying
anything run-time for good for nothing dynamic localization garbage.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com.

No comments: