- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by Adrian Lienhard

Hi Andrey, I once made the interpreter simulator work in 3.9 and posted my changes to http://bugs.squeak.org/view.php?id=6555 In there I fixed the method that you are missing as follows: !ByteSymbol methodsFor: '*VMMaker' stamp: 'al 7/23/2007 10:17'! coerceTo: cTypeString sim: interpreter ^self! ! You may also need to check the other fixes in the Mantis issue. Please report back how it works and what changes you needed so that we can integrate what is missing in Pharo and suggest changes to David for the VMMaker package. Cheers, Adrian BTW, a stack trace is written to a file in the directory where your image is located. On Sep 5, 2009, at 19:35 , StÃ©phane Ducasse wrote: > I do not know the answer but this would be great to get the > interpreter back on track. > > Stef > > On Sep 5, 2009, at 7:03 PM, Andrey Larionov wrote: > >> I attach screenshot of debugger to better understanding of context >> (why not provide in debuger an stacktrace exporter, or i miss >> somthing?) >> >> >> On Sat, Sep 5, 2009 at 20:53, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr >>> wrote: >>> Let us know if you find and we need to react in pharo. >>> >>> Stef >>> >>> On Sep 5, 2009, at 6:16 PM, David T. Lewis wrote: >>> >>>> I'm sorry, I did not read your original posting carefully enough. >>>> The >>>> classes that implement coerceTo:sim: are Integer, Array, Bitmap, >>>> CArray, >>>> and CObjectAccessor. So I do not know what the problem is in this >>>> case. >>>> Sorry for the confusion. >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> <Interpreter.png>_______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2009

Re: [Pharo-project] small pharo success story

by Adrian Lienhard

Cool. I added an entry to http://www.pharo-project.org/about/success-stories Cheers, Adrian On Sep 5, 2009, at 16:01 , Marcus Denker wrote: > Hi, > > 2Denker now has it's first iPhone app deployed and in the store that > uses a Pharo backend: > > http://2denker.de/findabike (german only) > > The app shows the bikes of DB (German Railway Company): http://en.wikipedia.org/wiki/Call_a_Bike > > On the phone, we use a standard Objective-C frontend. It gets the data > via http from a pharo server. > > > Marcus > > > -- > Marcus Denker -- marcus(a)2denker.de > http://www.2denker.de > > 2denker UG (haftungsbeschrÃ¤nkt) > Sitz KÃ¶ln > Amtsgericht - Registergericht - KÃ¶ln, HRB 65065 > GeschÃ¤ftsfÃ¼hrer: Christian Denker und Dr. Marcus Denker > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2009

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by StÃ©phane Ducasse

I do not know the answer but this would be great to get the interpreter back on track. Stef On Sep 5, 2009, at 7:03 PM, Andrey Larionov wrote: > I attach screenshot of debugger to better understanding of context > (why not provide in debuger an stacktrace exporter, or i miss > somthing?) > > > On Sat, Sep 5, 2009 at 20:53, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr > > wrote: >> Let us know if you find and we need to react in pharo. >> >> Stef >> >> On Sep 5, 2009, at 6:16 PM, David T. Lewis wrote: >> >>> I'm sorry, I did not read your original posting carefully enough. >>> The >>> classes that implement coerceTo:sim: are Integer, Array, Bitmap, >>> CArray, >>> and CObjectAccessor. So I do not know what the problem is in this >>> case. >>> Sorry for the confusion. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > <Interpreter.png>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2009

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by Andrey Larionov

I attach screenshot of debugger to better understanding of context (why not provide in debuger an stacktrace exporter, or i miss somthing?) On Sat, Sep 5, 2009 at 20:53, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> wrote: > Let us know if you find and we need to react in pharo. > > Stef > > On Sep 5, 2009, at 6:16 PM, David T. Lewis wrote: > >> I'm sorry, I did not read your original posting carefully enough. The >> classes that implement coerceTo:sim: are Integer, Array, Bitmap, >> CArray, >> and CObjectAccessor. So I do not know what the problem is in this >> case. >> Sorry for the confusion. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 5, 2009

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by StÃ©phane Ducasse

Let us know if you find and we need to react in pharo. Stef On Sep 5, 2009, at 6:16 PM, David T. Lewis wrote: > I'm sorry, I did not read your original posting carefully enough. The > classes that implement coerceTo:sim: are Integer, Array, Bitmap, > CArray, > and CObjectAccessor. So I do not know what the problem is in this > case. > Sorry for the confusion.

Sept. 5, 2009

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by StÃ©phane Ducasse

On Sep 5, 2009, at 4:50 PM, David T. Lewis wrote: > Hi Stef, > > I believe you have already done this, so nothing more needs to be > done. In fact I did the VMMaker changes, Mantis bug report, and Squeak > trunk fixes all based on the cleanup that you did for Pharo :) :) Yes I remember now cleaning a lot of that. Somehow I'm sad that squeak did not move before we started because it would have avoided to lose a lot of time. People may think that we did pharo for fun but noone like me wrote 2 books on squeak, and did so many squeak presentation, teaching material... anyway now we will continue pharo because it deserves its own flow. > If you need to double check this, the change set with all of the > methods that got moved is LeftoverMethodsMoveToVMMaker-dtl-M7221.2.cs > on the Mantis 7221 page. But I think it is all done now so no worries. >

Sept. 5, 2009

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by David T. Lewis

I'm sorry, I did not read your original posting carefully enough. The classes that implement coerceTo:sim: are Integer, Array, Bitmap, CArray, and CObjectAccessor. So I do not know what the problem is in this case. Sorry for the confusion. Dave On Sat, Sep 05, 2009 at 07:10:28PM +0400, Andrey Larionov wrote: > I recive this error (DNU Object>>coerceTo: sim:) on latest VMMaker > > On Sat, Sep 5, 2009 at 18:50, David T. Lewis<lewis(a)mail.msen.com> wrote: > > Hi Stef, > > > > I believe you have already done this, so nothing more needs to be > > done. In fact I did the VMMaker changes, Mantis bug report, and Squeak > > trunk fixes all based on the cleanup that you did for Pharo :) > > > > If you need to double check this, the change set with all of the > > methods that got moved is LeftoverMethodsMoveToVMMaker-dtl-M7221.2.cs > > on the Mantis 7221 page. But I think it is all done now so no worries. > > > > Dave > > > > On Sat, Sep 05, 2009 at 04:40:47PM +0200, St?phane Ducasse wrote: > >> Hi david > >> > >> do you have a list of the methods that we should remove from the image? > >> > >> Stef > >> > >> On Sep 5, 2009, at 4:33 PM, David T. Lewis wrote: > >> > >> > On Sat, Sep 05, 2009 at 04:19:51AM +0400, Andrey Larionov wrote: > >> >> I'm post an issue > >> >> http://code.google.com/p/pharo/issues/detail?id=1173 > >> >> Looks like call of > >> >> ? ?aDisplayText form: > >> >> in MorphicUIManage>>composeFormFor: is redundant > >> >> > >> >> Found during trying to run InterpreterSimulator (i realy want to help > >> >> improve project). > >> >> After i add accessor, i recieve an DNU of ByteSymbol>>coerceTo:sim: > >> >> > >> >> Is any have any idea. Is this method missing in VMMaker package or > >> >> removed in Pharo. > >> > > >> > Hi Andrey, > >> > > >> > We moved a number of these methods from Pharo (and Squeak) into > >> > the VMMaker package because they are part of the C code generator > >> > for Slang. ?They had been left in the image by accident. If you > >> > load the latest VMMaker from SqueakSource, this problem will be > >> > resolved. For background on this, see: > >> > > >> > ?http://bugs.squeak.org/view.php?id=7221 > >> > > >> > If you need to use an older VMMaker for some reason, I put a change > >> > set on the Mantis report that will let you load the missing methods > >> > (LeftoverMethodsMoveToVMMaker-dtl-M7221.2.cs). > >> > > >> > Dave > >> > > >> > > >> > _______________________________________________ > >> > Pharo-project mailing list > >> > Pharo-project(a)lists.gforge.inria.fr > >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2009

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by Andrey Larionov

I recive this error (DNU Object>>coerceTo: sim:) on latest VMMaker On Sat, Sep 5, 2009 at 18:50, David T. Lewis<lewis(a)mail.msen.com> wrote: > Hi Stef, > > I believe you have already done this, so nothing more needs to be > done. In fact I did the VMMaker changes, Mantis bug report, and Squeak > trunk fixes all based on the cleanup that you did for Pharo :) > > If you need to double check this, the change set with all of the > methods that got moved is LeftoverMethodsMoveToVMMaker-dtl-M7221.2.cs > on the Mantis 7221 page. But I think it is all done now so no worries. > > Dave > > On Sat, Sep 05, 2009 at 04:40:47PM +0200, St?phane Ducasse wrote: >> Hi david >> >> do you have a list of the methods that we should remove from the image? >> >> Stef >> >> On Sep 5, 2009, at 4:33 PM, David T. Lewis wrote: >> >> > On Sat, Sep 05, 2009 at 04:19:51AM +0400, Andrey Larionov wrote: >> >> I'm post an issue >> >> http://code.google.com/p/pharo/issues/detail?id=1173 >> >> Looks like call of >> >> Â Â aDisplayText form: >> >> in MorphicUIManage>>composeFormFor: is redundant >> >> >> >> Found during trying to run InterpreterSimulator (i realy want to help >> >> improve project). >> >> After i add accessor, i recieve an DNU of ByteSymbol>>coerceTo:sim: >> >> >> >> Is any have any idea. Is this method missing in VMMaker package or >> >> removed in Pharo. >> > >> > Hi Andrey, >> > >> > We moved a number of these methods from Pharo (and Squeak) into >> > the VMMaker package because they are part of the C code generator >> > for Slang. Â They had been left in the image by accident. If you >> > load the latest VMMaker from SqueakSource, this problem will be >> > resolved. For background on this, see: >> > >> > Â http://bugs.squeak.org/view.php?id=7221 >> > >> > If you need to use an older VMMaker for some reason, I put a change >> > set on the Mantis report that will let you load the missing methods >> > (LeftoverMethodsMoveToVMMaker-dtl-M7221.2.cs). >> > >> > Dave >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 5, 2009

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by David T. Lewis

Hi Stef, I believe you have already done this, so nothing more needs to be done. In fact I did the VMMaker changes, Mantis bug report, and Squeak trunk fixes all based on the cleanup that you did for Pharo :) If you need to double check this, the change set with all of the methods that got moved is LeftoverMethodsMoveToVMMaker-dtl-M7221.2.cs on the Mantis 7221 page. But I think it is all done now so no worries. Dave On Sat, Sep 05, 2009 at 04:40:47PM +0200, St?phane Ducasse wrote: > Hi david > > do you have a list of the methods that we should remove from the image? > > Stef > > On Sep 5, 2009, at 4:33 PM, David T. Lewis wrote: > > > On Sat, Sep 05, 2009 at 04:19:51AM +0400, Andrey Larionov wrote: > >> I'm post an issue > >> http://code.google.com/p/pharo/issues/detail?id=1173 > >> Looks like call of > >> aDisplayText form: > >> in MorphicUIManage>>composeFormFor: is redundant > >> > >> Found during trying to run InterpreterSimulator (i realy want to help > >> improve project). > >> After i add accessor, i recieve an DNU of ByteSymbol>>coerceTo:sim: > >> > >> Is any have any idea. Is this method missing in VMMaker package or > >> removed in Pharo. > > > > Hi Andrey, > > > > We moved a number of these methods from Pharo (and Squeak) into > > the VMMaker package because they are part of the C code generator > > for Slang. They had been left in the image by accident. If you > > load the latest VMMaker from SqueakSource, this problem will be > > resolved. For background on this, see: > > > > http://bugs.squeak.org/view.php?id=7221 > > > > If you need to use an older VMMaker for some reason, I put a change > > set on the Mantis report that will let you load the missing methods > > (LeftoverMethodsMoveToVMMaker-dtl-M7221.2.cs). > > > > Dave > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2009

Re: [Pharo-project] Issue with DisplayText and InterpreterSimulator

by StÃ©phane Ducasse

Hi david do you have a list of the methods that we should remove from the image? Stef On Sep 5, 2009, at 4:33 PM, David T. Lewis wrote: > On Sat, Sep 05, 2009 at 04:19:51AM +0400, Andrey Larionov wrote: >> I'm post an issue >> http://code.google.com/p/pharo/issues/detail?id=1173 >> Looks like call of >> aDisplayText form: >> in MorphicUIManage>>composeFormFor: is redundant >> >> Found during trying to run InterpreterSimulator (i realy want to help >> improve project). >> After i add accessor, i recieve an DNU of ByteSymbol>>coerceTo:sim: >> >> Is any have any idea. Is this method missing in VMMaker package or >> removed in Pharo. > > Hi Andrey, > > We moved a number of these methods from Pharo (and Squeak) into > the VMMaker package because they are part of the C code generator > for Slang. They had been left in the image by accident. If you > load the latest VMMaker from SqueakSource, this problem will be > resolved. For background on this, see: > > http://bugs.squeak.org/view.php?id=7221 > > If you need to use an older VMMaker for some reason, I put a change > set on the Mantis report that will let you load the missing methods > (LeftoverMethodsMoveToVMMaker-dtl-M7221.2.cs). > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 5, 2009