December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] removing class instead of method

by StÃ©phane Ducasse

Yes this is probably this sequence that happened to me too. stef On Dec 5, 2009, at 5:31 PM, Lukas Renggli wrote: >>> If you use the refactoring engine there are two distinct menu items: >>> >>> refactor class > remove >> The problem is that I never can remember what I did to get in that bad state. >> I would really remove remove class from the method menus. >> I hate it! > > It happens to me when I have selected a method, but the focus is on > the class and I press Ctrl+X. It has nothing to do with the > refactoring engine, that has no keyboard shortcut anyway. > > 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

Dec. 5, 2009

Re: [Pharo-project] Protocol extension proposal: Boolean>>asBit ?

by csrabak＠bol.com.br

I understand the motivation and the implementation, but IMNHO the name of the method should be #asSmallInteger or if you want more general #asNumber. Returning 1 or 0 is not the same thing as returning a bit, except if we agree on creating a class called bit where the operations on it abide to what it is expected for a bit. my .019999... -- Cesar Rabak Em 05/12/2009 08:44, Igor Stasenko < siguctua(a)gmail.com > escreveu: I currently writing a code which looks like: a := some numeric expression + (someBoolean ifTrue: [1] ifFalse: [0]). And i get somewhat tired repeating the same pattern in multiple places. So, i thinking , maybe #asBit convenience method could be useful? True>>asBit ^ 1 False>>asBit ^ 0 so, then, in case of need like above, we could write much shorter expressions: a := some numeric expression + someBoolean asBit. And its much less error prone comparing to #ifTrue:ifFalse:, since i found its relatively easy to make a mess (swapping 1 with 0), especially, when you having negations in expression, because once you see: (someBoolean not ifTrue: [1] ifFalse: [0]) you always tempted to write it as: (someBoolean ifTrue: [0] ifFalse: [1]). or as: (someBoolean ifFalse: [1] ifTrue: [0]). but once you start playing with it, its very easy to shoot into own feet if you are not careful. But if we could add #asBit, then we could write: someBoolean not asBit which is much more: a) concise & cleaner b) error proof -- 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

Dec. 5, 2009

Re: [Pharo-project] squeak VM 5.0

by David T. Lewis

Hi, (cc to vm-dev list) The 64-bit image that I provided is a direct descendent of the original one that was produced by Dan and Ian. Original 64-bit image: http://squeakvm.org/squeak64/dist3/Squeak64-3.8g-6548.image.tar.gz My update: http://squeakvm.org/squeak64/sq64-dtl.zip The original one was produced with a specialized system tracer, the code for which is here: http://squeakvm.org/squeak64/dist3/ChangeSets/System-Tracing.2.cs I did *not* use the system tracer to produce the updated image. Instead, it is the original image with various updates that I made over the years to keep up with VM developments (which were not entirely backward compatible). The original image will not run on a current VM, and that is the reason that I posted my update. The system tracer (including the specialized 64-bit one) does not work on little-endian machines. Somebody (tm) should fix this one of these days. There are a couple of Mantis reports related to this: http://bugs.squeak.org/view.php?id=5240 http://bugs.squeak.org/view.php?id=5239 As far as producing a 64-bit Pharo image, I think there are two things that could be tried: 1) Fix the system tracer to work on little-endian boxes (probably not too difficult), then try tracing some Pharo and Squeak images into 64-bit format. 2) Find somebody who has a big-endian Mac available, and have them try tracing some images. I can think of no reason why the newer images with closure support could not be traced into 64-bit formats, but I guess the only way to find out is to try it and see what happens. Dave On Fri, Dec 04, 2009 at 01:39:28PM -0800, John M McIntosh wrote: > I think David Lewis made the last one, let's cc him. > > Perhaps the process would be > > Examine the squeak image. > take the required source that does the system tracing > someone make a MC project (no idea if one exists?) > > a) file that into a Pharo image. > b) Correct things like references to Smalltalk, versus SmalltalkImage current > c) run it. > d) place 64bit image on pharo server. > > I note to run the system tracer you need to run it either on a PowerPC. > Or on a MacIntel using a 4.x series macintosh VM, make a copy, do a get info on the VM > check "Open using Rosetta" > > If "Open using Rosetta" is not an option and you are running 10.6 then it is likely you did > not install Rosetta when you upgraded/installed 10.6. You need to find your 10.6 DVD > and lookup how to install Rosetta after installing 10.6 > > PS yes you could use a 10.5 series VM for this too. > > > However to complicate things I don't think anyone has done a Closure based image > and I don't know if that will be a problem. You could take a pre-closure Pharo image > and try it just to get past the point where having the SystemTracer code in a MC is done. > > > On 2009-12-04, at 1:23 PM, Laval Jannik wrote: > > > Hi Alex, > > > > PharoCore is a 32bits image. > > So it works on Squeak.5.0.0.b9.64*32.app. > > > > I see that Squeak has a 64bits fork image, is it possible to have a Pharo one? > > What is the process to do this ? > > > > Cheers, > > Jannik > >

Dec. 5, 2009

Re: [Pharo-project] How do I know which issues are resolved in each new release?

by csrabak＠bol.com.br

OK! I'll swamped until the end of this week, but will look for information on this approach. I think I'll need to assemble an account in Twitter for myself also :-| -- Cesar Rabak Em 05/12/2009 08:28, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr > escreveu: we can use soap for example and I would really like to have an nice example :) Stef On Dec 4, 2009, at 7:55 PM, csrabak(a)bol.com.br wrote: > Marcus, > > This brings a question to me: is there a sort of API or web service we could use (obviously > for calling from inside Pharo) to post at the Pharo's Twitter account? > > I surmise that doing that for the blog would be 'easier' :-) > > -- > Cesar Rabak > > > Em 04/12/2009 10:09, Marcus Denker < denker(a)acm.org > escreveu: > > > Hello, > > Yes, we should improve information on what changed.... I would want to have a changelog for any image that is downloaded. And we should use the Blog. And Twitter. And. And. > We will do all that, but not today :-) > > Marcus > > _______________________________________________ > 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

Dec. 5, 2009

Re: [Pharo-project] christmas coding parties?

by Mariano Martinez Peck

Ok, here is the invitation: http://www.doodle.com/mn4e6anmskwpd5s7 If someone wants the admin link, let me know in a private email. Cheers, Mariano On Sat, Dec 5, 2009 at 5:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > > > > > > > Ok. So, it is 18h at what time ? 9 or 11? is this a pharo sprint or > whatever? > > > > whatever :) > > > > > address ? > > > > We can either do it at the university or at my place but I have to check > with my wife ;) > > > > > > hahahah ok. Let me know. Because when I create the doodle schedule, the > address is asked. > > > > what address? > write Lille :) > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 5, 2009

Re: [Pharo-project] SmallDictionary>>removeAll or >>empty?

by Lukas Renggli

SmallDictionary comes from the refactoring engine. It is a highly optimized dictionary originally intended for parse-tree matching. The method #empty does not make sense outside that context. The method #removeAll is implemented in Collection. I don't think that this implementation can ever work in any concrete collection implementation, because it modifies the collection while iterating over it (lint would know that). Most classes override it with something sensible though. Lukas 2009/12/5 Simon Denier <Simon.Denier(a)inria.fr>: > Stupid question: how do I remove all entities from a SmallDictionary > > Let's take: > d := SmallDictionary new. > d add: $d -> 4. > d add: $e -> 5. > d > > If I do > d empty > > then d size = 0 and d do: behaves as if there is nothing > BUT someone can still perform > d at: $d -> 5 > > If I do > d removeAll > > I get a MessageNotUnderstood: SmallInteger>>key > because #removeAll inherited from Collection expects a different > structure > > -- > Â Simon > > > > > _______________________________________________ > 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

Dec. 5, 2009

Re: [Pharo-project] removing class instead of method

by Lukas Renggli

>> If you use the refactoring engine there are two distinct menu items: >> >> Â refactor class > remove > The problem is that I never can remember what I did to get in that bad state. > I would really remove remove class from the method menus. > I hate it! It happens to me when I have selected a method, but the focus is on the class and I press Ctrl+X. It has nothing to do with the refactoring engine, that has no keyboard shortcut anyway. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 5, 2009

Re: [Pharo-project] Protocol extension proposal: Boolean>>asBit ?

by Lukas Renggli

> how do they are named in alien or FFI? I don't remember. I just vaguely think that both have convertor methods to transform the object to a low-level representation that can be directly used in external function calls. > This is two simple and trivial methods. There are so many other stuff that make no sense to have that > I would be ok to keep these ones. The question is if the proposed solution is generally useable? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 5, 2009

[Pharo-project] SmallDictionary>>removeAll or >>empty?

by Simon Denier

Stupid question: how do I remove all entities from a SmallDictionary Let's take: d := SmallDictionary new. d add: $d -> 4. d add: $e -> 5. d If I do d empty then d size = 0 and d do: behaves as if there is nothing BUT someone can still perform d at: $d -> 5 If I do d removeAll I get a MessageNotUnderstood: SmallInteger>>key because #removeAll inherited from Collection expects a different structure -- Simon

Dec. 5, 2009

Re: [Pharo-project] removing class instead of method

by StÃ©phane Ducasse

On Dec 5, 2009, at 5:14 PM, Lukas Renggli wrote: >> from time to time I get my class removed instead of a method. >> Is there a menu entry allowing to do that on the **method** menu items. >> Because this is really annoying. > > Happened to me too. > > If you use the refactoring engine there are two distinct menu items: > > refactor class > remove The problem is that I never can remember what I did to get in that bad state. I would really remove remove class from the method menus. I hate it! Stef > refactor method > remove > > Lukas > > 2009/12/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Hi >> >> >> 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

Dec. 5, 2009