On Tue, Apr 30, 2024 at 09:52:05AM -0400, Patrick Robb wrote: > On Sun, Apr 28, 2024 at 3:46 AM Mattias Rönnblom <hof...@lysator.liu.se> > wrote: > > > It would be great if the unit test suite (app/test/*) was compiled (and > > run) using a C++ (C++11) compiler as well. At least, if such is available. > > > > Sure, the UNH Lab can try this. > > > > > > With the current state of affairs, header file macros or functions are > > not verified to be functional (or even valid) C++. > > > > "C is a subset of C++", which was never true, is becoming less and less so. > > > > If all unit tests aren't valid C++, maybe one could start with an "opt > > in" model. > > > > Okay, so basically run the fast-test suite, record all that don't pass, > submit a bugzilla ticket stating which unit tests are not valid on a > certain c++ compiler, then bring CI Testing online using the valid subset > of fast-tests. This should work.
this seems like a reasonable approach. > > > > > > A drawback of this is that the unit tests need to be both valid C and > > valid C++. > >
