If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...

If you have a not-so-usual solution for your problems but need to justify it to your boss...

If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...

...then 'No Bugs' Hare on Soft.ware might be the right place for you.

Your mileage may vary. Batteries not included

Assorted Rants Tagged ‘C/C++’, page 1:

Java vs C++: Trading UB for Semantic Memory Leaks (Same Problem, Different Punishment for Failure)

posted October 30, 2018 by "No Bugs" Hare

Quote:	“with all due disrespect to mutable static/global data, I have to say that the problem of semantic memory leaks is NOT restricted to statics”
Another Quote:	“semantics of good code is about the same regardless of Java/C++ choice”
	[→]

posted October 3, 2018 by "No Bugs" Hare

Quote:	“we MUST NOT care about compiler internals beyond our task definition (which is based on (a) humans, and (b) hardware, that’s it).”
Another Quote:	“My problem with introducing a ‘model of the compiler’ into the picture, is that it can be used to justify pretty much anything without any relation to real-world requirements.”
	[→]

posted July 4, 2018 by "No Bugs" Hare

Quote:	“if you DO want to get performance from changing mallocs, make sure to test them with your own app”
Another Quote:	“in our humble opinion, overall winner so far (by a nose) is jemalloc.”
	[→]

posted June 21, 2018 by "No Bugs" Hare

Quote:	“We won’t ever get (almost) any virtual memory back, plain and simple”
Another Quote:	“relocation allows not only to reduce fragmentation, but to eliminate it entirely.”
	[→]

posted June 7, 2018 by "No Bugs" Hare

Quote:	“‘unchecked’ std::errors are treated as ‘something which should never ever happen, but in practice MAY occur as a result of potentially-recoverable bug'”
Another Quote:	“Failing-Fast does NOT mean we should necessarily Fail-Hard(!). In certain (production!) cases, Failing-Fast-AND-Soft IS a substantially better alternative.”
	[→]

posted May 30, 2018 by "No Bugs" Hare

Quote:	“having an ability to associate extra information with std::error is important for us – both for our own std::error exceptions, and for conversion from existing C++ exceptions”
Another Quote:	“I think that current C++ standard is Badly Lacking(tm) a concept of ‘segfault’ (which is supported by CPUs on VAST majority of modern systems with modern C++ compilers)”
	[→]

posted May 23, 2018 by "No Bugs" Hare

Quote:	“No single error handling method is good enough for ALL the projects – which in turn leads to segmentation, with some of the projects using exceptions, and some others using error codes”
Another Quote:	“Right above I said that I like the std::error exception proposal a.k.a.[P0709R0]. However, as soon as I look at competing proposals, I begin to love it.”
	[→]