irwir

> I guess you're referring to #8490 ? It's not clear to me in this thread what is wrong. Question, 'What was right?' might be asked. Yet again, there were...

> Early include also makes possible to remove some Windows headers from other files, but this should be in other PRs. Test build of the VS solution passed successfully with...

Windows 10 22H2 32-bit with the latest updates. Deleted old `Rapr.exe`, log and configuration, there is no `Rapr` directory in the profile. Version 0.12.64 is fine; starting from 0.12.82 it...

In case of failure it makes sense to provide the complete environment information: library version or commit, configuration, compiler. It seems my tests with the current _development head_ were not...

A recent issue in other project: different headers with the same name, all in the include path. The result - compilation failure.

4 `common.h` files in total; and duplication of _framework_ files adds one more. So five in total. Edit. 2 `service.h` (3 with duplication of _framework_).

> I can't think of any build failures due to headers with the same base name. One case has been already mentioned (March, 18, not mbedTLS library): different versions of...

> My only weak argument from my reading of the issue was: name too common, but that's not obviously the case. Common or not, it still causes inconvenience. Quoting from...

> I consider that a fairly weak argument: most IDEs should show an unambiguous name. Unfortunately, well known IDEs such as Visual Studio or RAD Studio do not know they...

> It did have one non-trivial consequence: we were accidentally relying on the the inclusion of `` in `check_config.h` in several files. Possibly this could be fixed with `` included...