[cfe-dev] More C++11 Migration Tools

Vane, Edwin edwin.vane at intel.com
Fri Nov 2 05:39:10 PDT 2012

> Personally, I'd rather see us refactor in place to get the architecture we like,
> then start building that out with additional migration steps. If adding a new
> migration step isn't super-easy, we should go refactor some more.

Alright. First question I have about such a multi-pass tool would be how best to do the rewriting. Should we completely apply the previous pass' changes, re-parse, then move on to the next pass? For simple transforms rewrites probably wouldn't conflict (e.g. template space removal, nullptr usage) but one could easily forsee one pass making a change that might affect a later pass. Let's not forget that physical rewrites from one pass may overlap with rewrites from another. Assuming yes, I presume we shouldn't be writing out to disk every time but rather changing an in-memory buffer?

Edwin Vane
  Software Developer
  Intel of Canada, Inc.

More information about the cfe-dev mailing list