<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 4, 2012, at 1:32 PM, Kim Gräsman <<a href="mailto:kim.grasman@gmail.com">kim.grasman@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">HI Micah,<br><br>On Thursday, October 4, 2012, Villmow, Micah wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Chris, the problem with steps #2/#3 is that plenty of clients have forward declarations of TargetData and the typedef won't work in this case, so I need to update the clients anyways.<br>
<a></a></blockquote><div> </div><div>One trick I've used as an alternative to typedefs is to just derive from the old class, e.g.</div><div><br></div><div> class NewName : public TargetData {};</div><div><br></div><div>
This is forward-declarable just as well as TargetData itself.</div></blockquote><br></div><div>Good idea. Micah, your first patch looks good to me, please commit. Can you use the subclass trick to make the next ones incremental like we discussed?</div><div><br></div><div>-Chris</div><br></body></html>