[PATCH] Model Deallocator node in CFG

Jordan Rose jordan_rose at apple.com
Wed Jan 29 11:09:45 PST 2014

  I actually think we can treat the deallocator as part of the 'delete' expression itself, rather than modifying the CFG. It may be a bit asymmetric, but the only real reason to have the separate allocator element in the CFG is so that it gets properly sequenced with the constructor. For the delete expression, the natural place to evaluate it is after the destructor is called, which already has a separate CFG node. What do you think?


More information about the cfe-commits mailing list