September 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] 64 bit

by Mariano Martinez Peck

Sorry, maybe I was not clear enough. You DO NOT need to have a 64 bits image + VM to make it work in a 64 bits OS/Processor. All you need is the 32 bits libraries of the OS. Why do you want a 64 bits image? On Thu, Sep 8, 2011 at 9:52 AM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > > > On Wed, Sep 7, 2011 at 2:39 PM, Milan Mimica <milan.mimica(a)gmail.com>wrote: > >> Hello list! >> >> I was wondering, are you going to provide a 64-bit OneClick package >> any time soon? When and what does that depend on? >> > > mmm not sure. Compile the VM in 64 bits is not that complicated. Problem is > that some plugins do not work with 64 bits VM, like FFI. > > >> If not, how do I go about building my own 64-bit image on linux? >> >> > I think we already tried. Maybe it was using SystemTracer. For example, > here is a 64 bits image: > https://gforge.inria.fr/frs/download.php/26274/PharoCore64-1.1-11196-UNSTAB… > > Notice that when using VM + image in 64 bits right now, we are NOT taking > advantage of all its 64 bits. I mean, you may be able to make it work out of > the box in a 64 bits machine/OS but that doesn't mean that the VM + image is > using really using the 64. Maybe 32 bits of them are zero ;) > Anyway, at some point in the future, we will have real 64 bits vm, a new > object format/header, etc. But not sure it will be "soon". > > Cheers > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

Sept. 8, 2011

Re: [Pharo-project] 64 bit

by Mariano Martinez Peck

On Wed, Sep 7, 2011 at 2:39 PM, Milan Mimica <milan.mimica(a)gmail.com> wrote: > Hello list! > > I was wondering, are you going to provide a 64-bit OneClick package > any time soon? When and what does that depend on? > mmm not sure. Compile the VM in 64 bits is not that complicated. Problem is that some plugins do not work with 64 bits VM, like FFI. > If not, how do I go about building my own 64-bit image on linux? > > I think we already tried. Maybe it was using SystemTracer. For example, here is a 64 bits image: https://gforge.inria.fr/frs/download.php/26274/PharoCore64-1.1-11196-UNSTAB… Notice that when using VM + image in 64 bits right now, we are NOT taking advantage of all its 64 bits. I mean, you may be able to make it work out of the box in a 64 bits machine/OS but that doesn't mean that the VM + image is using really using the 64. Maybe 32 bits of them are zero ;) Anyway, at some point in the future, we will have real 64 bits vm, a new object format/header, etc. But not sure it will be "soon". Cheers -- Mariano http://marianopeck.wordpress.com

Sept. 8, 2011

Re: [Pharo-project] Fwd: A new way to render the debugger

by Damien Cassou

On Wed, Sep 7, 2011 at 6:09 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Do you like it ? (Should it be integrated ?) What happens when the a frame is a closure? In the standard debugger you see the full closure code and you have to scroll to see the method in which it is implemented. Does your view improve this situation? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 8, 2011

Re: [Pharo-project] TextLint for Emacs & TextMate

by Damien Cassou

On Wed, Sep 7, 2011 at 1:24 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: >> Coral could be useful, but is it ready and working on Linux, Windows and MacOS? > > So? you're opposed to refactoring? Not at all. Let me rephrase: Coral would be really great, I even tried to use it. Unfortunately, it looks like it doesn't currently work on Linux. If you can make it work on all platforms, I would certainly like to see it replace the current awkward mechanism I've introduced in TextLint. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 8, 2011

Re: [Pharo-project] 64 bit

by Damien Cassou

On Wed, Sep 7, 2011 at 2:39 PM, Milan Mimica <milan.mimica(a)gmail.com> wrote: > how do I go about building my own 64-bit image on linux? you can try to follow Mariano's blog posts: http://marianopeck.wordpress.com/2011/03/31/journey-through-the-vm/. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 8, 2011

Re: [Pharo-project] A new way to render the debugger

by Tudor Girba

+1 Doru On 8 Sep 2011, at 08:14, Max Leske wrote: > Awesome! > > > On 08.09.2011, at 07:17, HwaJong Oh wrote: > >> I like it. >> Reads nice. >> >> -- >> View this message in context: http://forum.world.st/Fwd-A-new-way-to-render-the-debugger-tp3796782p379789… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

Sept. 8, 2011

Re: [Pharo-project] Find & Replace analysis

by StÃ©phane Ducasse

do you want to participate to the basicWidgets chapter for the new book? Stef On Sep 8, 2011, at 3:36 AM, HwaJong Oh wrote: > I learning how to use polymorph. > > http://appdal.com/groups/36442/wiki/9165a/attachments/f3fdb/Pharo%20GUI%20F… > > > HwaJong Oh > > -- > View this message in context: http://forum.world.st/Find-Replace-analysis-tp3797664p3797664.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Sept. 8, 2011

Re: [Pharo-project] [BUG]Socket(Object)>>primitiveFailed:

by laurent laffont

On Wed, Sep 7, 2011 at 11:27 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 07 Sep 2011, at 21:32, laurent laffont wrote: > > > On SmallHarbour we use a modified VM (only SecurityPlugin - > https://gitorious.org/~laurentlaffont/cogvm/smallharbour ) so an image > can open only a given set of ports. Each image / account has an allocated > port number, so when an image starts a .st file is given as argument which > stop all seaside adaptors and then start Zinc Seaside adaptor on a given > port. > > > > The problem is: if I have saved a image with a socket opened on port XX, > then try to start it on SmallHarbour on port YY - given that XX is forbidden > - image crashes. > > Apart from the fact that I think we have a serious problem here, see > > http://code.google.com/p/pharo/issues/detail?id=4768 > > (but nobody seems to care, no one even confirmed that this happens for them > too) > Now I care :) As we use a modified VM I'll try to make it reproduceable easily. I will tell you. (Anyway on SmallHarbour server itself it's easy. If you want access .....) > the workaround is (as I said to Lukas, and as I do myself) not to save > images with a running server and just start the adaptor in a startup .st > file. > Yes but for Pier this is a problem as the image is autosaved so when you restart it through SmallHarbour web interface there's a running server. Laurent. > HTH, > > Sven > > >

Sept. 8, 2011

[Pharo-project] Important mail important mail important mail

by StÃ©phane Ducasse

Hi guys Some of you may have the impression that we focus on the wrong bugs and fixes. Indeed the bugs of the debugger are important and the one of the server too. Now let us face reality - how can we deal with the bugs if there are not described with a way to reproduce them - how can we deal with bugs if we do not know if this is a bug or not For example, if the behavior worked in previous version or not if the behavior works in 1.4 - then let us imagine that some behavior looks like a bug: question was is the impact of fixing it. Because may be the strange behavior is just used in a lot of places. So do we change it or not. Come on DO YOU IMAGINE THE AMOUNT OF WORK IT IS? So if we want to make progress we have to sort the bug tracker (and so far we do not like it because we cannot really group bug in subproject - sometimes we have 30 min to do something and not 3 hours - should we abandon all the little fixes to concentrate on "more important one" - Now the killing question: how many of you read bug entries and try to reproduce them? So may be we should put the bug tracker in read only so that we can get some work done. Now you can help by just looking at bug entries and writing if they are feature request, real bugs, wished behavior, Stef

Sept. 8, 2011

Re: [Pharo-project] [BUG]Socket(Object)>>primitiveFailed:

by StÃ©phane Ducasse

On Sep 7, 2011, at 11:27 PM, Sven Van Caekenberghe wrote: > > On 07 Sep 2011, at 21:32, laurent laffont wrote: > >> On SmallHarbour we use a modified VM (only SecurityPlugin - https://gitorious.org/~laurentlaffont/cogvm/smallharbour ) so an image can open only a given set of ports. Each image / account has an allocated port number, so when an image starts a .st file is given as argument which stop all seaside adaptors and then start Zinc Seaside adaptor on a given port. >> >> The problem is: if I have saved a image with a socket opened on port XX, then try to start it on SmallHarbour on port YY - given that XX is forbidden - image crashes. > > Apart from the fact that I think we have a serious problem here, see > > http://code.google.com/p/pharo/issues/detail?id=4768 > > (but nobody seems to care, no one even confirmed that this happens for them too) This is not that nobody cares, this is that this is the week of the the restart of everything and spending days in travels and meetings. And yes we should really find the bug that hangs the tests on the server and that one. Stef > > the workaround is (as I said to Lukas, and as I do myself) not to save images with a running server and just start the adaptor in a startup .st file. > > HTH, > > Sven > >

Sept. 8, 2011