Style?

[frobnitzem]

heat.C uses lots of globals. Most egregious is static bool update_solution(). It also has mixed C and C++ functionality (like #include <ostream> and class Double (with static globals) in Double.H), but snprintf/fprintf in utils.C.
Fixing both would upgrade the coding style IMHO.

[markcmiller86]

Good points. It evolved from a single .c file code. OTOH, this is an app, not a lib. I don't expect to link heat.C or its friends into anything as a lib. But, maybe its worth designing that way anyway?

For globals, keeping in mind that these are used in various separate compilation modules, what would you recommend? I was thinking creating either a namespace or single global variable of type struct that encapsulated all of them.

IMHO, C-lib printf is much easier for handling nitty-gritty formatting than C++ iostream.

Would be happy to entertain a PR 😃

[markcmiller86]

Could put all the extern statements in heat.H