- Pharo-dev - lists.pharo.org

[Pharo-project] pharo dev 1.1 & Cog
by Norbert Hartl Sept. 22, 2010

Sept. 22, 2010

I tried to launch the latest pharo dev 1.1 with vm 5.8b10 and it crashes. Is this known to cause problems or should it work? thanks, Norbert

2 2

Re: [Pharo-project] Webpage for research paper about Pharo?
by StÃ©phane Ducasse Sept. 22, 2010

Sept. 22, 2010

Yes I would prefer to see that as success stories than documentation On Sep 22, 2010, at 3:55 PM, Henrik Johansen wrote: > I liked http://pharo-project.org/about/research better, but I guess that's just me :) > To me, it belongs more with mission description and success stories than tutorials and screencasts. > > Cheers, > Henry > > On Sep 22, 2010, at 3:13 35PM, Alexandre Bergel wrote: > >> Everybody agrees on http://pharo-project.org/documentation/pharo-in-research >> ? >> >> C

2 1

Re: [Pharo-project] Issue 2996: Base64MimeConverter with multiline option
by StÃ©phane Ducasse Sept. 22, 2010

Sept. 22, 2010

Thanks I will integrate it in the next batch. Stef On Sep 22, 2010, at 4:20 PM, Denis Kudriashov wrote: > Hello, > > I integrate squeak behavior of Base64MimeConverter for multiline option. See Issue 2996 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Issue 2996: Base64MimeConverter with multiline option
by Denis Kudriashov Sept. 22, 2010

Sept. 22, 2010

Hello, I integrate squeak behavior of Base64MimeConverter for multiline option. See Issue 2996 <http://code.google.com/p/pharo/issues/detail?id=2996>

1 0

[Pharo-project] Fwd: [Vm-dev] Weak finalization enh. are still not integrated into VM(s)
by Andreas Wacknitz Sept. 22, 2010

Sept. 22, 2010

Hi guys, are there any plans to integrate this in Pharo? As I want to do some experiments with Magma I am specially interested in Pharo-1.1 for it. Regards, Andreas Anfang der weitergeleiteten E-Mail: > Von: "David T. Lewis" <lewis(a)mail.msen.com> > Datum: 22. September 2010 05:23:36 MESZ > An: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org>, siguctua(a)gmail.com > Betreff: Re: [Vm-dev] Weak finalization enh. are still not integrated into VM(s) > Antwort an: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > > On Tue, Sep 21, 2010 at 04:22:22PM +0300, Igor Stasenko wrote: >> >> On 21 September 2010 06:20, David T. Lewis <lewis(a)mail.msen.com> wrote: >>> >>> On Tue, Sep 21, 2010 at 03:28:35AM +0300, Igor Stasenko wrote: >>>> >>>> I am also uploaded a slice of system changes with new classes & rest >>>> of stuff into inbox: >>>> >>>> >>>> CollectionsTests-Igor.Stasenko.169 >>>> Collections-Igor.Stasenko.370 >>>> Kernel-Igor.Stasenko.478 >>>> System-Igor.Stasenko.358 >>>> >>>> note, that despite of these changes, system are still using old >>>> WeakRegistry instance, >>>> and obviously 'WeakRegistry default' needs to be modified to be >>>> replaced with new functionality. >>> >>> These inbox changes are out of date with respect to the trunk, so >>> would need to be merged with care. >> >> Yeah, i did not updated the image before applying changesets. >> >>> But aside from that, is there >>> any reason that your changes should *not* be moved into trunk now? >>> If no objections, then we should include them now. >>> >> >> There are a couple of doits, which should be invoked after loading changes: >> >> WeakArray restartFinalizationProcess >> and of couse >> Smalltalk recreateSpecialObjectsArray >> >> Btw, i found that in image i was using, >> Smalltalk specialObjectsArray size >> was 50 >> while in #recreateSpecialObjectsArray method there was already 55 entries >> (and with weak finalization it should be 56). > > This should already be updated in trunk: > > Name: System-dtl.333 > Author: dtl > Time: 25 May 2010, 9:00:22.752 pm > Ancestors: System-spd.332 > Update SmalltalkImage>>recreateSpecialObjectsArray for support of Alien and improved > finalization (Mantis 7473). Corresponding VM support is in SqS/VMMaker-dtl.175. > > So after a #recreateSpecialObjectsArray the size is 56, and the last slot > is used for WeakFinalizer if present in the image. > > I think that everything is ready for your WeakFinalizer updates. Unless > there are any other issues, please just go ahead and commit them to trunk. > > :) > > Dave > >> >>> I understand that the VM changes are not yet available in the >>> official VMs, but this should be corrected the next time that new >>> VMs are distributed. >>> >>> Dave >>> >>> >> Thanks, David. >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig.

2 2

Re: [Pharo-project] Fwd: [Vm-dev] Weak finalization enh. are still not integrated into VM(s)
by StÃ©phane Ducasse Sept. 22, 2010

Sept. 22, 2010

thanks for your effort. Stef On Sep 22, 2010, at 3:41 PM, Igor Stasenko wrote: > 2010/9/22 Andreas Wacknitz <a.wacknitz(a)gmx.de>: >> Hi guys, >> are there any plans to integrate this in Pharo? >> As I want to do some experiments with Magma I am specially interested in >> Pharo-1.1 for it. >> Regards, >> Andreas >> > > Yes, i will put changesets into pharo issue tracker, to integrate it > with Pharo as well. > >> Anfang der weitergeleiteten E-Mail: >> >> Von: "David T. Lewis" <lewis(a)mail.msen.com> >> Datum: 22. September 2010 05:23:36 MESZ >> An: Squeak Virtual Machine Development Discussion >> <vm-dev(a)lists.squeakfoundation.org>, siguctua(a)gmail.com >> Betreff: Re: [Vm-dev] Weak finalization enh. are still not integrated into >> VM(s) >> Antwort an: Squeak Virtual Machine Development Discussion >> <vm-dev(a)lists.squeakfoundation.org> >> >> >> On Tue, Sep 21, 2010 at 04:22:22PM +0300, Igor Stasenko wrote: >> >> On 21 September 2010 06:20, David T. Lewis <lewis(a)mail.msen.com> wrote: >> >> On Tue, Sep 21, 2010 at 03:28:35AM +0300, Igor Stasenko wrote: >> >> I am also uploaded a slice of system changes with new classes & rest >> >> of stuff into inbox: >> >> >> CollectionsTests-Igor.Stasenko.169 >> >> Collections-Igor.Stasenko.370 >> >> Kernel-Igor.Stasenko.478 >> >> System-Igor.Stasenko.358 >> >> note, that despite of these changes, system are still using old >> >> WeakRegistry instance, >> >> and obviously 'WeakRegistry default' needs to be modified to be >> >> replaced with new functionality. >> >> These inbox changes are out of date with respect to the trunk, so >> >> would need to be merged with care. >> >> Yeah, i did not updated the image before applying changesets. >> >> But aside from that, is there >> >> any reason that your changes should *not* be moved into trunk now? >> >> If no objections, then we should include them now. >> >> >> There are a couple of doits, which should be invoked after loading changes: >> >> WeakArray restartFinalizationProcess >> >> and of couse >> >> Smalltalk recreateSpecialObjectsArray >> >> Btw, i found that in image i was using, >> >> Smalltalk specialObjectsArray size >> >> was 50 >> >> while in #recreateSpecialObjectsArray method there was already 55 entries >> >> (and with weak finalization it should be 56). >> >> This should already be updated in trunk: >> >> Name: System-dtl.333 >> Author: dtl >> Time: 25 May 2010, 9:00:22.752 pm >> Ancestors: System-spd.332 >> Update SmalltalkImage>>recreateSpecialObjectsArray for support of Alien and >> improved >> finalization (Mantis 7473). Corresponding VM support is in >> SqS/VMMaker-dtl.175. >> >> So after a #recreateSpecialObjectsArray the size is 56, and the last slot >> is used for WeakFinalizer if present in the image. >> >> I think that everything is ready for your WeakFinalizer updates. Unless >> there are any other issues, please just go ahead and commit them to trunk. >> >> :) >> >> Dave >> >> >> I understand that the VM changes are not yet available in the >> >> official VMs, but this should be corrected the next time that new >> >> VMs are distributed. >> >> Dave >> >> >> Thanks, David. >> >> >> -- >> >> Best regards, >> >> Igor Stasenko AKA sig. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Pharocasts: Document with HelpSystem
by laurent laffont Sept. 22, 2010

Sept. 22, 2010

You will learn how to: - write an HelpSystem book - use PackageAPIHelpBuilder to generate the API documentation of a package - create your own builder to dynamically create a documentation from the system Starting from now, no excuses to not write documentation ;) http://pharocasts.blogspot.com/2010/09/document-with-helpsystem.html Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

3 2

Re: [Pharo-project] Fwd: [Vm-dev] Weak finalization enh. are still not integrated into VM(s)
by StÃ©phane Ducasse Sept. 22, 2010

Sept. 22, 2010

Thanks David too many emails and flood of information. Stef On Sep 22, 2010, at 2:20 PM, David T. Lewis wrote: > FYI, the change sets were posted on Mantis, so you can use that for > reference also. I'm not sure if these are the final versions, but they > should be close. > > http://bugs.squeak.org/view.php?id=7473 > > Dave > > On Wed, Sep 22, 2010 at 10:52:37AM +0200, St?phane Ducasse wrote: >> Andreas >> >> we cannot simply merge package of squeak (we would get all their changes and we have to sort). >> I asked igor to see if he can publish code to be integrated in pharo. >> >>> are there any plans to integrate this in Pharo? >> >> Yes but we do not have the time. >> Again for the weak changes somebody with a bit of time and concentration can help. >> So far we cannot. >> >>> As I want to do some experiments with Magma I am specially interested in Pharo-1.1 for it. >>> >>> Regards, >>> Andreas >>> >>>>>>> I am also uploaded a slice of system changes with new classes & rest >>>>>>> of stuff into inbox: >>>>>>> >>>>>>> >>>>>>> CollectionsTests-Igor.Stasenko.169 >>>>>>> Collections-Igor.Stasenko.370 >>>>>>> Kernel-Igor.Stasenko.478 >>>>>>> System-Igor.Stasenko.358 >>>>>>> >>>>>>> note, that despite of these changes, system are still using old >>>>>>> WeakRegistry instance, >>>>>>> and obviously 'WeakRegistry default' needs to be modified to be >>>>>>> replaced with new functionality. >>>>>> >>>>>> These inbox changes are out of date with respect to the trunk, so >>>>>> would need to be merged with care. >>>>> >>>>> Yeah, i did not updated the image before applying changesets. >>>>> >>>>>> But aside from that, is there >>>>>> any reason that your changes should *not* be moved into trunk now? >>>>>> If no objections, then we should include them now. >>>>>> >>>>> >>>>> There are a couple of doits, which should be invoked after loading changes: >>>>> >>>>> WeakArray restartFinalizationProcess >>>>> and of couse >>>>> Smalltalk recreateSpecialObjectsArray >>>>> >>>>> Btw, i found that in image i was using, >>>>> Smalltalk specialObjectsArray size >>>>> was 50 >>>>> while in #recreateSpecialObjectsArray method there was already 55 entries >>>>> (and with weak finalization it should be 56). >>>> >>>> This should already be updated in trunk: >>>> >>>> Name: System-dtl.333 >>>> Author: dtl >>>> Time: 25 May 2010, 9:00:22.752 pm >>>> Ancestors: System-spd.332 >>>> Update SmalltalkImage>>recreateSpecialObjectsArray for support of Alien and improved >>>> finalization (Mantis 7473). Corresponding VM support is in SqS/VMMaker-dtl.175. >>>> >>>> So after a #recreateSpecialObjectsArray the size is 56, and the last slot >>>> is used for WeakFinalizer if present in the image. >>>> >>>> I think that everything is ready for your WeakFinalizer updates. Unless >>>> there are any other issues, please just go ahead and commit them to trunk. >>>> >>>> :) >>>> >>>> Dave >>>> >>>>> >>>>>> I understand that the VM changes are not yet available in the >>>>>> official VMs, but this should be corrected the next time that new >>>>>> VMs are distributed. >>>>>> >>>>>> Dave >>>>>> >>>>>> >>>>> Thanks, David. >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko AKA sig. >>> >>> _______________________________________________ >>> 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

1 0

Re: [Pharo-project] Fwd: [Vm-dev] Weak finalization enh. are still not integrated into VM(s)
by StÃ©phane Ducasse Sept. 22, 2010

Sept. 22, 2010

Andreas we cannot simply merge package of squeak (we would get all their changes and we have to sort). I asked igor to see if he can publish code to be integrated in pharo. > are there any plans to integrate this in Pharo? Yes but we do not have the time. Again for the weak changes somebody with a bit of time and concentration can help. So far we cannot. > As I want to do some experiments with Magma I am specially interested in Pharo-1.1 for it. > > Regards, > Andreas > >>>>> I am also uploaded a slice of system changes with new classes & rest >>>>> of stuff into inbox: >>>>> >>>>> >>>>> CollectionsTests-Igor.Stasenko.169 >>>>> Collections-Igor.Stasenko.370 >>>>> Kernel-Igor.Stasenko.478 >>>>> System-Igor.Stasenko.358 >>>>> >>>>> note, that despite of these changes, system are still using old >>>>> WeakRegistry instance, >>>>> and obviously 'WeakRegistry default' needs to be modified to be >>>>> replaced with new functionality. >>>> >>>> These inbox changes are out of date with respect to the trunk, so >>>> would need to be merged with care. >>> >>> Yeah, i did not updated the image before applying changesets. >>> >>>> But aside from that, is there >>>> any reason that your changes should *not* be moved into trunk now? >>>> If no objections, then we should include them now. >>>> >>> >>> There are a couple of doits, which should be invoked after loading changes: >>> >>> WeakArray restartFinalizationProcess >>> and of couse >>> Smalltalk recreateSpecialObjectsArray >>> >>> Btw, i found that in image i was using, >>> Smalltalk specialObjectsArray size >>> was 50 >>> while in #recreateSpecialObjectsArray method there was already 55 entries >>> (and with weak finalization it should be 56). >> >> This should already be updated in trunk: >> >> Name: System-dtl.333 >> Author: dtl >> Time: 25 May 2010, 9:00:22.752 pm >> Ancestors: System-spd.332 >> Update SmalltalkImage>>recreateSpecialObjectsArray for support of Alien and improved >> finalization (Mantis 7473). Corresponding VM support is in SqS/VMMaker-dtl.175. >> >> So after a #recreateSpecialObjectsArray the size is 56, and the last slot >> is used for WeakFinalizer if present in the image. >> >> I think that everything is ready for your WeakFinalizer updates. Unless >> there are any other issues, please just go ahead and commit them to trunk. >> >> :) >> >> Dave >> >>> >>>> I understand that the VM changes are not yet available in the >>>> official VMs, but this should be corrected the next time that new >>>> VMs are distributed. >>>> >>>> Dave >>>> >>>> >>> Thanks, David. >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] Colstme in September
by Alexander LazareviÄ Sept. 22, 2010

Sept. 22, 2010

Hi! Just a short reminder that the next Cologne Smalltalk Meetup will be happening next Thursday at the usual time and location. For any details have a look at [1]. Cheers, Alex [1] http://colstme.selfish.org/events/2010.4-Stammtisch

1 0