Dmitry Kuteynikov

v1.20.9.0 Messed up native windows application window

@CHR, @Daniel Marjamäki - many thanks! Both your solutions works (the define and the library specification). This doesn't resolve some other issues with int128, namely bit shifts, but "this is another story". Thanks a lot!

It's recommended way to mark custom gcc types like __int128 so gcc -Wpedantic won't complain that they're not ISO. My attempts on reducing example in mostly same way resulted in no complains from cppcheck... That's my luck... ;-)

It's recommended way to mark custom gcc types like __int128 so gcc -Wpedantic won't complain that they're not ISO. My attempts on reducing example in mostly same way resulted in no complains from cppcheck... That's my luck... ;-)

It's recommended way to mark custom gcc types like __int128 so cppcheck won't complain about 'em. My attempts on reducing example in mostly same way resulted in no complains from cppcheck... That's my luck... ;-)

It's recommended way to mark custom gcc types like __int128 so cppcheck won't complain about 'em.

Ok. I did it. It compiles and cppcheck says bad words. Took quite a few attempts. There are two pair of files besides CMakeLists.txt. HashTable - support stuff that doesn't really matters, most everything cut out anyway. HashTableInteger - the templated class in question, whose methods are FP-ed as uninitialized variables. Just in case: Cppcheck 1.90

Ok. I did it. It compiles and cppcheck says bad words. Took quite a few attempts. There are two pair of files besides CMakeLists.txt. HashTable - support stuff that doesn't really matters, most everything cut out anyway. HashTableInteger - the templated class in question, whose methods are FP-ed as uninitialized variables.