On 19.03.2010, at 11:08, Henrik Johansen wrote:
On Mar 19, 2010, at 10:53 23AM, Bert Freudenberg wrote:
On 19.03.2010, at 10:44, Henrik Johansen wrote:
the method will probably be renamed again in Pharo, to #primFindSubstring:in:startingAt:matchTable:
I see no compelling reason why we shouldn't just apply the same refactoring to Squeak? KISS ;)
- Bert -
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
The reason I didn't propose it is I didn't want to be seen as forcing Squeak to change just because Pharo changed. (Although, as should be clear from the previous mails I think it's a superior solution to what is in Squeak now)
It sounds sensible to me, and there is no policy in place to Just Be Different ;)
I bet if you published a package with the refactoring to the trunk inbox (open to submissions for all) it would very soon be merged.
VMMaker would have to be changed either way to stay compatible :)
Cheers, Henry
- Bert -