On Sat, Nov 6, 2010 at 8:21 PM, Esteban Lorenzanoestebanlm@gmail.comwrote:
I mean... 2hs and still not finished :(
On 2010-11-06 20:18:59 -0300, Esteban Lorenzanoestebanlm@gmail.com said:
mmm... now the "inlining step X" is taking for years... is that normal?
Cheers, Esteban
On 07.11.2010 04:57, David T. Lewis wrote:
No of course it is not normal, and as Eliot said you are probably stuck in a recursion for some reason or another. Use<alt>-period to interrupt and get a debugger to find out what went wrong.
On Sun, Nov 07, 2010 at 11:32:04AM +0100, Henrik Sperre Johansen wrote:
IIRC, it's because in Pharo the method included in MiscPrimitivePlugin, String>>#findSubstring..., is no longer the primitive, it's been moved to findSubstringViaPrimitive... findSubstring... now checks whether the primitive will work for the parameters (WideStrings vs ByteStrings), before it actually calls the primitive. To "fix" this for Pharo, change the method included in MiscPrimitivePlugin's "this is where my code should be located"-method.
Cheers, Henry
PS. Most of these issues have been discussed here before, do a search of the list and you are likely to find answers to speedbumps encountered along the way. Most notably, there's a MonticelloConfiguration which, as part of loading VMMaker, will modify it/the image in the ways needed for it to work on Pharo.
Thanks, that may well be the problem that Mariano is seeing. In addition to discussion on the list, it is also documented in the bug report that you opened in Mantis (thank you for doing this!):
http://bugs.squeak.org/view.php?id=7479
I think that the proposed solution in Mantis 7479 is too fragile for my tastes. IMO the obvious solution is to fix the problem where it orginated, in the Pharo image. If that cannot be accomplished, then someone might want to just reimplement the primitive as an ordinary primitive (but that is not something that I am working on).
Dave