News for hackers. Stuff that matters.
Re:Orthodox C++ by RcouF1uZ4gsC on Wednesday May 22, 2024 @06:07PM (#40447284)
This guideline is basically banning the use of std::string.

Having a string abstraction beyond C null-terminated string is a huge deal both for convenience and for safety. It is super easy to get strings wrong in C.

This is also one of the reasons why printf won't work. You cannot pass a type like std::string to a variable args function.

Re:Orthodox C++ by cmovq on Wednesday May 22, 2024 @07:37PM (#40448289)
I can understand banning it. It’s important to understand std::string is more of a string builder implementation, which is rarely what you want, but people treat it as the default way to handle strings in C++.

Too often I have to fix code that makes liberal use of std::string, making copies and allocations everywhere for no apparent reason, when string_view or better const char* would do.

Re:Orthodox C++ by throw4023042q0 on Wednesday May 22, 2024 @06:44PM (#40447679)
> This is also one of the reasons why printf won't work. You cannot pass a type like std::string to a variable args function.

Can't you just call .c_str() on the std::string first to get to the null-terminated char array? https://cplusplus.com/reference/string/string/c_str/

Re:Orthodox C++ by hot_gril on Wednesday May 22, 2024 @06:17PM (#40447387)
Was gonna say, this guide is too light on examples. So an example of string usage would be passing around null-terminated char arrays.
Re:Orthodox C++ by humanrebar on Wednesday May 22, 2024 @06:18PM (#40447396)
std::string_view with %.*s as a string formatter work well enough if you're set on using printf.
Re:Orthodox C++ by gpderetta on Wednesday May 22, 2024 @06:21PM (#40447419)
I have to use std::string_view with %.*s as a string formatter every day. It is an incredible pain. Of course the solution is getting rid of printf style formatting, not string_view.
Re:Orthodox C++ by o11c on Wednesday May 22, 2024 @06:45PM (#40447692)
The hardest part of passing `std::string` to `printf` was getting the macro to convince the pre-standard-C++11 compiler that it was `constexpr` enough so that `-Werror=format` would work.

I found it was easiest to sometimes allocate a temporary, if the input wasn't known to be NUL-terminated.

Re:Orthodox C++ by jeffbee on Wednesday May 22, 2024 @06:25PM (#40447462)
Are you suggesting

  printf("%.*s", static_cast<int>(sv.size()), sv.data())

?
Re:Orthodox C++ by humanrebar on Wednesday May 22, 2024 @06:34PM (#40447566)
Well, wrap it up in something more ergonomic, but it works. I'm usually putting strings into some sort of I/O API (like a logger) instead of hardcoding copies to stdout everywhere.

https://stackoverflow.com/a/72575650

Re:Orthodox C++ by jeffbee on Wednesday May 22, 2024 @06:54PM (#40447779)
Wrap it way up into something ergonomic and idiomatic, like fmt.
Re:Orthodox C++ by humanrebar on Wednesday May 22, 2024 @08:12PM (#40448661)
Sure. I do. But there are tradeoffs even then. Look at the error messages compared to printf for example.
Re:Orthodox C++ by AnimalMuppet on Wednesday May 22, 2024 @06:45PM (#40447687)

  std::string str;
  printf("%s\n", str.c_str());