Disclosure: On this site you won’t find specific advice on “how to call function xyz()”. Interpreting C++ ARM and #pragma dwim is also out of scope.

We’re treating our readers as intelligent beings who can use Google and/or StackOverflow, where all such specific questions were answered more than once.

What you will find is opinions, more opinions, and even more opinions on all the aspects of software development - and with a large chunk of them based on real-world experience too.

Your mileage may vary. Batteries not included.

The Curse of External Fragmentation: Relocate or Bust!

June 21, 2018 by “No Bugs” Bunny

freed_pages_32_and_128_per_page.png

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.

Filed under: On.ProgrammingOptimizations

Read more

How to consume an HTTP API

June 11, 2018 by “No Bugs” Bunny

Consuming API

Quote:

Programs are not the self-contained, self-reliant, self-sufficient things they once were.

Another Quote:

I highly recommend you log every HTTP request you send and every HTTP response you receive.

Filed under: On.ProgrammingTips and Tricks

Read more

Unchecked Exceptions for C++

June 7, 2018 by “No Bugs” Bunny

failquadrant-4.png

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.

Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingProgramming LanguagesOn.DevelopmentDevelopment Philosophy

Tagged With: C/C++
Read more

App-level Developer on std::error Exceptions Proposal for C++. Part II. The Discussion.

May 30, 2018 by “No Bugs” Bunny

BB_emotionM_0017b.png

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++ exception

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)

Filed under: On.ProgrammingProgramming Languages

Tagged With: C/C++
Read more