w-peuker

Hi Marco, adding a single space after // also increases readability for humans. Therefore, many style guides prescribe this type of visual padding between the “frame” of the comment and its content.

Errors in help configuration index.ini

Could you please add your examples as text like this: ```cpp verbatim copy of your code section goes here ``` The images are very small and are placed in the wrong place when clicked. In addition, they cannot be copied to easily verify the problem and possible fixes. And finally: Which Artistic Style version do you use?

Could you please add your examples as text like this: ```cpp verbatim copy of your code section goes here ``` The images are very small and are placed in the wrong place when clicked. In addition, they cannot be copied to easily verify the problem and possible fixes. Which version are you using?

I don't think it's a good idea to change the actual code just to avoid incorrect formatting of the sources. Some compilers will optimize away the string concatenations, others will not, resulting in significant runtime degradation. A better way, also obvious for future reader, is to prevent formatting on portions of the code: // *INDENT-OFF* std::string test() { return "--" + boundaryString + "\r\n" "Content-Type: application/json; charset=UTF-8" "\r\n" /**/ "\r\n" + metaDataBuf + "\r\n" "--" + boundaryString...

I don't think it's a good idea to change the actual code just to avoid incorrect formatting of the sources. Some compilers will optimize away the string concatenations, others will not, resulting in significant runtime degradation. A better way, also obvious for future reader, is to prevent formatting on portions of the code: // *INDENT-OFF* std::string test() { return "--" + boundaryString + "\r\n" "Content-Type: application/json; charset=UTF-8" "\r\n" /**/ "\r\n" + metaDataBuf + "\r\n" "--" + boundaryString...