<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Mar 20, 2012, at 5:28 PM, Jordan Rose <<a href="mailto:jediknil@belkadan.com">jediknil@belkadan.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; display: inline !important; float: none; ">Fair enough. I'll go rework this. Advance question: is it better to wait until the whole path is generated before restarting, or to restart as soon as we see the interesting symbols have changed? Both ways could result in a second round of new interesting symbols.</span><br style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "></blockquote></div><br><div>I would just do the simplest thing possible. Generate the entire path by wrapping the calls to GenerateExtensivePathDiagnostic/GenerateMinimalPathDiagnostic in a while loop, check if the set of symbols have changed, and if so, drop the old path and repeat.</div><div><br></div><div>The performance issue here is likely non-existent. It takes a couple orders of magnitude more work to find the bug in the first place.</div></body></html>