<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 19, 2010, at 10:53 23AM, Bert Freudenberg wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>On 19.03.2010, at 10:44, Henrik Johansen wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">the method will probably be renamed again in Pharo, to #primFindSubstring:in:startingAt:matchTable:<br></blockquote><br>I see no compelling reason why we shouldn't just apply the same refactoring to Squeak? KISS ;)<br><br>- Bert -<br><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote>It doesn't solve the problem of hardcoded references from Plugins to the core image in the long run, but that'd certainly be a simple solution. :D</div><div><br></div><div>The reason I didn't propose it is I didn't want to be seen as forcing Squeak to change just because Pharo changed.</div><div> (Although, as should be clear from the previous mails I think it's a superior solution to what is in Squeak now)</div><div><br></div><div>VMMaker would have to be changed either way to stay compatible :)</div><div><br></div><div>Cheers,</div><div>Henry</div></body></html>