On Sep 27, 2010, at 10:40 PM, Marcin Świderski <[email protected]> wrote:
> > I've added some test cases. They can be later used to create regresion > > tests. > > For the test cases, how do you plan on testing it? Also, since these are all > small tests, please include them in one file (if possible). > > You did mention something about similar case in test folder, but I can't > currently locate your message. Some suggestions would be useful, e.g. how to > set up test for feature that is currently turned off. My suggestion was to look at plist-output.m, which tests the plist output (XML) for analyzer diagnostics. Instead of testing plist output, however, one could look at the cfg dump. To test the inclusion of dtors in the cfg, we should add another driver flag, similar to -dump-cfg, that would impact AnalysisConsumer. Then you could test the entire feature from the command line. Honestly, I don't think these changes should go in until we can test it in this fashion. _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
