We'd like to have a single tool for C++98 -> C++11 migration, and merely flags to enable (and disable) individual feature migrations within that tool.
Before we add a second tool (in addition to loop-convert) I'd like to actually make good on that design goal. My suggestion would be: 1) rename loop-convert to be something generic (cxx-migrate? cxx-update? cxx-modernize?) 2) start using a convention of '--convert-loops' and '--convert-foo' pattern of options that enable and disable specific conversions, and sink the loop stuff under it. ideally do this with a reasonable level of abstraction 3) Add this transform under '--convert-nullptr' similar to #2. This seem like a reasonable strategy? http://llvm-reviews.chandlerc.com/D136 _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
