Hi Petr,

I was thinking, maybe we do not need to match subsequent lines! We could just as well filter the individual warnings. For example, the following two warnings be filtered separately just fine (as you had done it, I’ve only modified the comments):

# we do not want to see the trace from the place of initialization...
.*when initialized here.*

# ...through all the place of instantiation
.*instantiated from here.*

All warnings of the two types will be filtered and what will remain is only the third kind of warning that is causing the other two. That is actually the one we need to fix.

The multi-line match pattern which you had before can be substituted with the simpler single-line regexps:

.*‘Protocols::BitTorrent::Torrents::FileInfo::.*’ should be initialized in the member initialization list

.*‘Protocols::BitTorrent::Torrents::Torrent::PrivateData::.*’ should be initialized in the member initialization list


Are there any other cases where you think multi-line match patterns would be useful? If not, I’d suggest that we drop support for them.

Best regards,

Peter