January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] 64 bit images (was Re: [squeak-dev] The Trunk: Collections-dtl.268.mcz)

by Laval Jannik

Hi, I made a new version of the system-tracer (in attachment). It works fine with the latest pharo version. For wordSize, we decide to create a instance variable in SmalltalkImage, which is initialized at startup. The method initialPC is: --- initialPC "Answer the program counter for the receiver's first bytecode." ^ (self numLiterals + 1) * SmalltalkImage current wordSize + 1 --- The fix will be integrated in Pharo soon. It is also in attachment. Cheers On Jan 3, 2010, at 06:46 , John M McIntosh wrote: > Ok, well I was hoping that Laval Jannik would review the changes/solution in http://bugs.squeak.org/view.php?id=7430 > then update his original System-Tracing.2forPharo3.cs Then test to confirm we can build a 64bit image from the current Pharo image > > > On 2010-01-02, at 6:46 PM, David T. Lewis wrote: > >> John, one additional note. >> >> The SystemTracer changesets currently in circulation have an obsolete >> implementation of SystemDictionary>>wordSize.The original 64-bit >> Squeak used vmParameterAt: 27 for the VM to answer its word size, >> but this was later changed to vmParameter at: 40. This is the reason >> that the original "dist3" 64-bit image does not work on current VMs. >> >> You will want to revert #wordSize back to a current version >> so that it uses vmParameter at: 40. >> >> This issue will go away when we implement the cached #wordSize fixes >> discussed separately (http://bugs.squeak.org/view.php?id=7430) but >> I wanted to mention it because I spotted the obsolete method in the >> System-Tracing2forPharo.cs change set. >> > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > --- Jannik Laval ---

Jan. 4, 2010

Re: [Pharo-project] [Seaside] Mac VM 5.2b1 ships

by Mariano Martinez Peck

John: Another problem I found is that I cannot open more than one image at the same time with this VM. Is this expected? Cheers Mariano On Sun, Jan 3, 2010 at 9:28 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi > > I asked abotu alien because at Amsterdam eliot used bird names to refer to > FFI > implementation. So I was thinking that building on top of Alien was a move > into the future. > May be you should talk with eliot. > > Stef > > > > 64-bit FFI will work on Unix and Windows with these fixes. I have not > > tried Mac, but I expect that some work would be needed. The changes > > are not trivial, and will affect the plugin, the VM itself, and the > > Pharo/Squeak images. > > > > The next big fix on our VM-team "to-do list" is to get sound working > > on 64-bit platforms, and FFI will come after that. > > > > I do not know the status of alien now, but my understanding is that > > it is limited to intel processors and 32-bit platforms. My guess is > > that it would be good to fix the old FFI first because those changes > > would likely have an impact on alien also. But I do not know much > > about alien, so I am not the best person to say. > > > > 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 >

Jan. 4, 2010

Re: [Pharo-project] about and:and: and and:

by Lukas Renggli

This very likely does not preserve the formatting. The rewrite completely restructures the AST. Lukas 2010/1/4 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > If this preserves formatting, proceed, else, beware. > Given there were few senders in trunk, my change was manual, not > automatic (Steph didn't you mean systematic ?). > > Nicolas > > 2010/1/4 Lukas Renggli <renggli(a)gmail.com>: >> From Slime: >> >> RBParseTreeRewriter new >> Â Â Â Â replace: '``@expr1 and: [ | `@temp2 | ``@expr2 ] and: [ | `@temp3 | ``@expr3 ]' >> Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 and: [ | `@temp2 | ``@expr2 and: [ | `@temp3 | ``@expr3 ] ]'; >> Â Â Â Â Â Â Â Â replace: '``@expr1 and: [ | `@temp2 | ``@expr2 ] and: [ | `@temp3 | >> ``@expr3 ] and: [ | `@temp4 | ``@expr4 ]' >> Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 and: [ | `@temp2 | ``@expr2 and: [ | `@temp3 | >> ``@expr3 and: [ | `@temp4 | ``@expr4 ] ] ]'; >> Â Â Â Â Â Â Â Â replace: '``@expr1 and: [ | `@temp2 | ``@expr2 ] and: [ | `@temp3 | >> ``@expr3 ] and: [ | `@temp4 | ``@expr4 ] and: [ Â | `@temp5 | ``@expr5 >> ]' >> Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 and: [ | `@temp2 | ``@expr2 and: [ | `@temp3 | >> ``@expr3 and: [ | `@temp4 | ``@expr4 and: [ | `@temp5 | ``@expr5 ] ] ] >> ]'; >> Â Â Â Â Â Â Â Â replace: '``@expr1 or: [ | `@temp2 | ``@expr2 ] or: [ | `@temp3 | ``@expr3 ]' >> Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 or: [ | `@temp2 | ``@expr2 or: [ | `@temp3 | ``@expr3 ] ]'; >> Â Â Â Â Â Â Â Â replace: '``@expr1 or: [ | `@temp2 | ``@expr2 ] or: [ | `@temp3 | >> ``@expr3 ] or: [ | `@temp4 | ``@expr4 ]' >> Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 or: [ | `@temp2 | ``@expr2 or: [ | `@temp3 | >> ``@expr3 or: [ | `@temp4 | ``@expr4 ] ] ]'; >> Â Â Â Â Â Â Â Â replace: '``@expr1 or: [ | `@temp2 | ``@expr2 ] or: [ | `@temp3 | >> ``@expr3 ] or: [ | `@temp4 | ``@expr4 ] or: [ | `@temp5 | ``@expr5 ]' >> Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 or: [ | `@temp2 | ``@expr2 or: [ | `@temp3 | >> ``@expr3 or: [ | `@temp4 | ``@expr4 or: [ | `@temp5 | ``@expr5 ] ] ] >> ]'; >> Â Â Â Â Â Â Â Â replace: '``@expr1 or: [ | `@temp2 | ``@expr2 ] or: [ | `@temp3 | >> ``@expr3 ] or: [ | `@temp4 | ``@expr4 ] or: [ | `@temp5 | ``@expr5 ] >> or: [ | `@temp6 | ``@expr6 ]' >> Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 or: [ | `@temp2 | ``@expr2 or: [ | `@temp3 | >> ``@expr3 or: [ | `@temp4 | ``@expr4 or: [ | `@temp5 | ``@expr5 or: [ | >> `@temp6 | ``@expr6 ] ] ] ] ]'; >> Â Â Â Â Â Â Â Â yourself >> >> 2010/1/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Nicolas >>> I would love to get the latest version cleanup automatically >>> If by accident a huge slice would be committed into the pharoInbox. >>> what the others think? >>> >>> Stef >>> >>> On Jan 4, 2010, at 9:26 AM, Nicolas Cellier wrote: >>> >>>> My point was: >>>> - these messages are Squeak specific >>>> - they are slow (didn't knew about NewCompiler...) >>>> - do they really add some value over nested and: ? >>>> >>>> Nicolas >>>> >>>> 2010/1/4 Lukas Renggli <renggli(a)gmail.com>: >>>>> The NewCompiler optimizes #and:and:and: to an optimized and nested >>>>> #and:. The standard compiler does a normal message send with block >>>>> activations for each condition and thus is dead slow. >>>>> >>>>> Lukas >>>>> >>>>> 2010/1/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>> hi nicolas >>>>>> >>>>>> I saw that you apply some automatic refactoring in squeak about and:and: -> and: >>>>>> and I wanted to know. Is and: more optimized than and:and: (I imagine that) but I would like >>>>>> to know for sure. >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Lukas Renggli >>>>> http://www.lukas-renggli.ch >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 4, 2010

[Pharo-project] Mac VM 5.2.b2 ships

by John M McIntosh

I've push the latest cocoa based 32/64bit macintel/powerpc VM There was a back-leveled patch for the JPEG2 read/writer which causes the Seasides tests to crash the VM. This is fixed. Look for the folder experimental/64bits in the regular places found via http://smalltalkconsulting.com/squeak.html or ftp://ftp.smalltalkconsulting.com/experimental/64bit/32bitImage*64bitVM/ file name: Squeak 64-32 5.2b2.app.zip This *beta* VM runs in 32 or 64 bit mode on macIntel, and 32bit mode on powerpc to support Squeak 32bit images. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 4, 2010

Re: [Pharo-project] What about killing PharoWeb images?

by Lukas Renggli

>> I basically >> build the Seaside images for me. > > Wait... The Seaside one click images and any other image that it is in the > seaside website is not for you. I guess they are for the public. No, they are not designed for the public, I build the images only for me. The fact that I put them on seaside.st is because people asked us to do so and this is really easy. If people like the images and it helps them, then this is great. If you are really into building images, you should build them for YOU and not for anybody else. Otherwise, I think, they are never going to fly. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 4, 2010

Re: [Pharo-project] Issues in 1.1 (was: Re: [update 1.1] #11126 - 27 (final ...))

by Igor Stasenko

hmm. i thought i fixed this one. 2010/1/4 Levente Uzonyi <leves(a)elte.hu>: > On Wed, 30 Dec 2009, StÃ©phane Ducasse wrote: > >> BIG THANKS igor!!! >> >> 11127 >> ----- >> >> - Issue 1690: New Method Trailer part 7 (cs 9) > > There are still some issues. Some methods (for example TPureBehavior >> > #addTraitSelector:withMethod:) still use the old trailer bytes #(0 0 0 0). > These should be removed asap (I had to make some surgery with #become: to > compile the new version.) > > > Levente > >> >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

Jan. 4, 2010

Re: [Pharo-project] about and:and: and and:

by Nicolas Cellier

If this preserves formatting, proceed, else, beware. Given there were few senders in trunk, my change was manual, not automatic (Steph didn't you mean systematic ?). Nicolas 2010/1/4 Lukas Renggli <renggli(a)gmail.com>: > From Slime: > > RBParseTreeRewriter new > Â Â Â Â replace: '``@expr1 and: [ | `@temp2 | ``@expr2 ] and: [ | `@temp3 | ``@expr3 ]' > Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 and: [ | `@temp2 | ``@expr2 and: [ | `@temp3 | ``@expr3 ] ]'; > Â Â Â Â Â Â Â Â replace: '``@expr1 and: [ | `@temp2 | ``@expr2 ] and: [ | `@temp3 | > ``@expr3 ] and: [ | `@temp4 | ``@expr4 ]' > Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 and: [ | `@temp2 | ``@expr2 and: [ | `@temp3 | > ``@expr3 and: [ | `@temp4 | ``@expr4 ] ] ]'; > Â Â Â Â Â Â Â Â replace: '``@expr1 and: [ | `@temp2 | ``@expr2 ] and: [ | `@temp3 | > ``@expr3 ] and: [ | `@temp4 | ``@expr4 ] and: [ Â | `@temp5 | ``@expr5 > ]' > Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 and: [ | `@temp2 | ``@expr2 and: [ | `@temp3 | > ``@expr3 and: [ | `@temp4 | ``@expr4 and: [ | `@temp5 | ``@expr5 ] ] ] > ]'; > Â Â Â Â Â Â Â Â replace: '``@expr1 or: [ | `@temp2 | ``@expr2 ] or: [ | `@temp3 | ``@expr3 ]' > Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 or: [ | `@temp2 | ``@expr2 or: [ | `@temp3 | ``@expr3 ] ]'; > Â Â Â Â Â Â Â Â replace: '``@expr1 or: [ | `@temp2 | ``@expr2 ] or: [ | `@temp3 | > ``@expr3 ] or: [ | `@temp4 | ``@expr4 ]' > Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 or: [ | `@temp2 | ``@expr2 or: [ | `@temp3 | > ``@expr3 or: [ | `@temp4 | ``@expr4 ] ] ]'; > Â Â Â Â Â Â Â Â replace: '``@expr1 or: [ | `@temp2 | ``@expr2 ] or: [ | `@temp3 | > ``@expr3 ] or: [ | `@temp4 | ``@expr4 ] or: [ | `@temp5 | ``@expr5 ]' > Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 or: [ | `@temp2 | ``@expr2 or: [ | `@temp3 | > ``@expr3 or: [ | `@temp4 | ``@expr4 or: [ | `@temp5 | ``@expr5 ] ] ] > ]'; > Â Â Â Â Â Â Â Â replace: '``@expr1 or: [ | `@temp2 | ``@expr2 ] or: [ | `@temp3 | > ``@expr3 ] or: [ | `@temp4 | ``@expr4 ] or: [ | `@temp5 | ``@expr5 ] > or: [ | `@temp6 | ``@expr6 ]' > Â Â Â Â Â Â Â Â Â Â Â Â with: '``@expr1 or: [ | `@temp2 | ``@expr2 or: [ | `@temp3 | > ``@expr3 or: [ | `@temp4 | ``@expr4 or: [ | `@temp5 | ``@expr5 or: [ | > `@temp6 | ``@expr6 ] ] ] ] ]'; > Â Â Â Â Â Â Â Â yourself > > 2010/1/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Nicolas >> I would love to get the latest version cleanup automatically >> If by accident a huge slice would be committed into the pharoInbox. >> what the others think? >> >> Stef >> >> On Jan 4, 2010, at 9:26 AM, Nicolas Cellier wrote: >> >>> My point was: >>> - these messages are Squeak specific >>> - they are slow (didn't knew about NewCompiler...) >>> - do they really add some value over nested and: ? >>> >>> Nicolas >>> >>> 2010/1/4 Lukas Renggli <renggli(a)gmail.com>: >>>> The NewCompiler optimizes #and:and:and: to an optimized and nested >>>> #and:. The standard compiler does a normal message send with block >>>> activations for each condition and thus is dead slow. >>>> >>>> Lukas >>>> >>>> 2010/1/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>> hi nicolas >>>>> >>>>> I saw that you apply some automatic refactoring in squeak about and:and: -> and: >>>>> and I wanted to know. Is and: more optimized than and:and: (I imagine that) but I would like >>>>> to know for sure. >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> http://www.lukas-renggli.ch >>>> >>>> _______________________________________________ >>>> 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 >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 4, 2010

Re: [Pharo-project] What about killing PharoWeb images?

by Mariano Martinez Peck

On Mon, Jan 4, 2010 at 9:45 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > > 1) First of all, I don't like the PharoWeb name. Because it is not Web in > > general, it is seaside. So, in my opinion, a better name would be > > PharoSeaside. Maybe even new comers may think that the only alternative > is > > seaside. You know I have nothing against Seaside and that I even use it > > several times. I would like to see AidaWeb images based in Pharo too. > > I think at some point the images also contained AIDA. No it doesn't. Not at least in the lasts images I have and in the scripts I have. > > > 4) Now I created all the Metacello configurations for the PharoDev image > and > > I took me a lot of time. Because I am not the developer of any of those > > projects. So, I need to understand the dependencies, the order, the > > versions, etc. But why ??? If Seaside people have already done that, > don't > > duplicate efforts. > > There is a configuration for Seaside 3.0 (and probably also Seaside > 2.8). This was probably the first configuration every written. Ask > Dale. > > yes, that's true. > > 4) You may notice that Seaside images are a bit "different" than our Dev > > images. This is mostly due to the preferences, the theme and maybe some > > tools (ECompeltion instead of OCompletion, etc..). So, what I suggest is > to > > prepare a little script that can be downloadable and those people who > want a > > Seaside image but more "similar" to our Dev images, just run that script. > > They are different because they reflect my preferences. yes, of course. That's why I propose a little "script" that changes that to something more like our "dev" images. > I basically > build the Seaside images for me. Wait... The Seaside one click images and any other image that it is in the seaside website is not for you. I guess they are for the public. > If other people like and use these > images, that's great of course. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 4, 2010

Re: [Pharo-project] Simple question about NewInspector

by Frederic Pluquet

RoelTyper is also used in ProtoObject>>niChildrenBlockForFixedFields (an extension for NewInspector). NewInspector can work without RoelTyper. The message "The last version of RoelTyper must be loaded to have this information" is shown when NewInspector tries to calculate types and that RoelTyper is not found. FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet On Sat, Dec 26, 2009 at 11:29 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi Frederic. I am trying to see if it make sense to create a metacello > configuration for NewInspector. The only external (not in PharoCore) > dependency I saw using the DependencyBrowser is RoelTyper, which is used in > the class NICompiledMethodNode >> configuration you use the class > TypeCollector which is from RoelTyper. > > So, the question is, is this dependency correct? I ask because I took a > PharoCore image, load NewINspector WITHOUT RoelTyper and it "seemed" to > work. > > Thank you very much. > > Mariano >

Jan. 4, 2010

Re: [Pharo-project] about and:and: and and:

by Lukas Renggli

Jan. 4, 2010