On Mon Aug 1 18:13:46 2022 +0000, R��mi Bernon wrote:
And imho winetest-like tests makes it easier to see what gets implemented and what is still not implemented. Yes, we can consider that the set of IDL code used by Wine is already a good enough test case and any severe breakage will break the build first, but if the build isn't broken already, it's still hard to tell the effect of some widl change before it gets used.
Maybe we could have a special "test" mode in widl (with #widl pragma or a command line option), which we could use to instruct widl to "expect failure" (and revert return code, probably silence or redirect output). The same could be used to trigger complete build (including proxy, stubs, typelibs, iids, depending on what IDL provides), but redirecting it all to /dev/null.