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

[Pharo-project] 1.1-11409-rc4dev10.07.2 - Transcript behaving strange

by Stanislav Paskalev

Hi everyone, I'm going through the first chapter of Pharo by Example and the Transcript morph behaves somewhat strange. When I type "Transcript show: " into a workspace, every time I press space 2 numbers are shown in the Transcript, they look like character indexes from the text from the workspace it self. I believe this is non intentional, perhaps some debugging output left over ? -- And let me congratulate everyone involved in Pharo, it looks really polished and makes a very good first impression for newcommers to Smalltalk like me :) Best regards, Stanislav Paskalev

July 21, 2010

Re: [Pharo-project] Is Object>>name important?

by Hernan Wilkinson

the same happens to me all the time... so I do as if it does not exist :-), I just override it... I agree it should not be Object's protocol. On Wed, Jul 21, 2010 at 1:08 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > ideally I would love to get rid of it and externalName and friends.... now > there are probably deep reasons for now. > > Stef > > On Jul 21, 2010, at 5:45 PM, Alexandre Bergel wrote: > > > Hi! > > > > Time to time, I need to create a #name method on my class. But I found a > bit ugly to do an override. > > Is Object>>name that important? > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > 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 >

July 21, 2010

Re: [Pharo-project] fold: ?

by StÃ©phane Ducasse

I like this point so we can include fold: then. Stef On Jul 21, 2010, at 7:15 PM, Lukas Renggli wrote: >>> Now I remember: We called it #reduce: because this is much more common >>> among programming languages. >> >> Really? http://en.wikipedia.org/wiki/Fold_(higher-order_function) > > Yes, reduce is typically used without initial value, while fold is > used with initial value (we already have inject:into: for that). > > Lukas > >> >> >> Levente >> >>> >>> The implementation in Pharo is much more general than the one of >>> Squeak. Pharo behaves the same as Squeak for two argument blocks on >>> SequenceableCollection. Squeak does not support anything else. >>> >>> Lukas >>> >>> On 21 July 2010 18:32, Lukas Renggli <renggli(a)gmail.com> wrote: >>>> >>>> Ahh, it is called #reduce:, #reduceLeft: and #reduceRight: in Pharo. >>>> >>>> Lukas >>>> >>>> On 21 July 2010 18:27, Lukas Renggli <renggli(a)gmail.com> wrote: >>>>> >>>>> See <http://code.google.com/p/pharo/issues/detail?id=2401>. Looks like >>>>> it never got merged though. >>>>> >>>>> Lukas >>>>> >>>>> On 21 July 2010 18:20, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>> wrote: >>>>>> >>>>>> hi lukas >>>>>> >>>>>> I thought that we introduced the equivalent when we were pair >>>>>> programming at my place. >>>>>> fold: got introduced in squeak and may be your implementation/API >>>>>> should be pushed there? >>>>>> 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 >>>>> www.lukas-renggli.ch >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> 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 > 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

July 21, 2010

Re: [Pharo-project] about hex

by StÃ©phane Ducasse

Thanks Cool analysis now my point is that it would make sense to have hex always returning 16rXX and printStringHex XX Stef > Well, it is. :) My question is about having a consistent API accross Character>>hex and Integer>>hex not about whether the behavior changed. > For Character >> #hex : > In Squeak 3.8: $a hex -> '16r61' > In Squeak 3.9: $a hex -> MNU SmallInteger >> #hex > In Squeak 3.10: $a hex -> '61' > In Squeak 4.0: $a hex -> '61' > In Squeak 4.1: $a hex -> '61' > In Squeak 4.2-alpha: $a hex -> '61' I got confused because since Character did a simple value hex and hex got changed when I reverted I captured the new behavior Still my question is valid. > $a hex -> '16r61' > In Squeak 4.1: 97 hex -> '61' > In Squeak 4.2-alpha: 97 hex -> '16r61' > > So Character >> #hex returns the same in Squeak 4.1 and 4.2, while Integer >> #hex doesn't. >

July 21, 2010

Re: [Pharo-project] fold: ?

by Lukas Renggli

>> Now I remember: We called it #reduce: because this is much more common >> among programming languages. > > Really? http://en.wikipedia.org/wiki/Fold_(higher-order_function) Yes, reduce is typically used without initial value, while fold is used with initial value (we already have inject:into: for that). Lukas > > > Levente > >> >> The implementation in Pharo is much more general than the one of >> Squeak. Pharo behaves the same as Squeak for two argument blocks on >> SequenceableCollection. Squeak does not support anything else. >> >> Lukas >> >> On 21 July 2010 18:32, Lukas Renggli <renggli(a)gmail.com> wrote: >>> >>> Ahh, it is called #reduce:, #reduceLeft: and #reduceRight: in Pharo. >>> >>> Lukas >>> >>> On 21 July 2010 18:27, Lukas Renggli <renggli(a)gmail.com> wrote: >>>> >>>> See <http://code.google.com/p/pharo/issues/detail?id=2401>. Looks like >>>> it never got merged though. >>>> >>>> Lukas >>>> >>>> On 21 July 2010 18:20, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> wrote: >>>>> >>>>> hi lukas >>>>> >>>>> I thought that we introduced the equivalent when we were pair >>>>> programming at my place. >>>>> fold: got introduced in squeak and may be your implementation/API >>>>> should be pushed there? >>>>> 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 >>>> www.lukas-renggli.ch >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> >> >> -- >> Lukas Renggli >> 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 www.lukas-renggli.ch

July 21, 2010

Re: [Pharo-project] about hex

by Levente Uzonyi

On Wed, 21 Jul 2010, StÃ©phane Ducasse wrote: > This is not the answer to my question. > I talked about character>>hex, please reread my mail. Well, it is. :) For Character >> #hex : In Squeak 3.8: $a hex -> '16r61' In Squeak 3.9: $a hex -> MNU SmallInteger >> #hex In Squeak 3.10: $a hex -> '61' In Squeak 4.0: $a hex -> '61' In Squeak 4.1: $a hex -> '61' In Squeak 4.2-alpha: $a hex -> '61' For Integer >> #hex : In Squeak 3.8: 97 hex -> '16r61' In Squeak 3.9: 97 hex -> MNU SmallInteger >> #hex In Squeak 3.10: 97 hex -> '61' In Squeak 4.0: 97 hex -> '61' In Squeak 4.1: 97 hex -> '61' In Squeak 4.2-alpha: 97 hex -> '16r61' So Character >> #hex returns the same in Squeak 4.1 and 4.2, while Integer >> #hex doesn't. Levente > > Stef > > > >> On Wed, 21 Jul 2010, Nicolas Cellier wrote: >> >>> I don't think Eliot changed that, he only changed Integer>>hex... >> >> He didn't change it compared to the previous implementation, but he didn't restore the pre 3.9 state. >> >>> It seems that every implementation of hex did avoid to print the radix in >>> Squeak 3.10. Was it intentional ? >>> >>> Anyway, it will be hard to reach homogeneity because: >>> Integer>>hex should print the radix for VMMaker compatibility >>> ByteArray>>hex shouldn't for cypto compatibility >> >> ByteArray >> #hex is in the Cryptography package, and IMHO it should stay there. >> >> >> Levente >> >>> >>> Nicolas >>> >>> 2010/7/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> >>>> Levente /Eliot >>>> >>>> I noticed that >>>> >>>> $A hex on squeak >>>> -> 41 >>>> and in pharo >>>> -> '16r41' >>>> >>>> I would like to have both consistent what do you think to have >>>> >>>> $A hex >>>> -> '16r41' >>>> >>>> $A printStringHex >>>> -> '41' >>>> >>>> like that this is consistent with the behavior on integer. >>>> Eliot I saw that to change the behavior on characters and I would like to >>>> know why. >>>> I thought that it was for debugging purpose. >>>> >>>> Stef >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >

July 21, 2010

[Pharo-project] [update 1.2] #12063

by StÃ©phane Ducasse

12063 ----- - Issue 2708: Cleaning a bit systemnavigation. - Issue 2701: fix duplicate entries handling in recentmessageset. Thanks benjamin - Issue 2702: Better duller from Squeak. - Issue 2689: random morph unused code cleanups - Issue 2699: Hex for Cog Stef (on holidays.... relaxing from latex for a day or two)

July 21, 2010

Re: [Pharo-project] fold: ?

by StÃ©phane Ducasse

We will not argue on that one! Stef On Jul 21, 2010, at 6:55 PM, Levente Uzonyi wrote: > On Wed, 21 Jul 2010, Lukas Renggli wrote: > >> Now I remember: We called it #reduce: because this is much more common >> among programming languages. > > Really? http://en.wikipedia.org/wiki/Fold_(higher-order_function) > > > Levente > >> >> The implementation in Pharo is much more general than the one of >> Squeak. Pharo behaves the same as Squeak for two argument blocks on >> SequenceableCollection. Squeak does not support anything else. >> >> Lukas >> >> On 21 July 2010 18:32, Lukas Renggli <renggli(a)gmail.com> wrote: >>> Ahh, it is called #reduce:, #reduceLeft: and #reduceRight: in Pharo. >>> >>> Lukas >>> >>> On 21 July 2010 18:27, Lukas Renggli <renggli(a)gmail.com> wrote: >>>> See <http://code.google.com/p/pharo/issues/detail?id=2401>. Looks like >>>> it never got merged though. >>>> >>>> Lukas >>>> >>>> On 21 July 2010 18:20, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>> hi lukas >>>>> >>>>> I thought that we introduced the equivalent when we were pair programming at my place. >>>>> fold: got introduced in squeak and may be your implementation/API should be pushed there? >>>>> 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 >>>> www.lukas-renggli.ch >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> >> >> -- >> Lukas Renggli >> 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

July 21, 2010

Re: [Pharo-project] about hex

by StÃ©phane Ducasse

This is not the answer to my question. I talked about character>>hex, please reread my mail. Stef > On Wed, 21 Jul 2010, Nicolas Cellier wrote: > >> I don't think Eliot changed that, he only changed Integer>>hex... > > He didn't change it compared to the previous implementation, but he didn't restore the pre 3.9 state. > >> It seems that every implementation of hex did avoid to print the radix in >> Squeak 3.10. Was it intentional ? >> >> Anyway, it will be hard to reach homogeneity because: >> Integer>>hex should print the radix for VMMaker compatibility >> ByteArray>>hex shouldn't for cypto compatibility > > ByteArray >> #hex is in the Cryptography package, and IMHO it should stay there. > > > Levente > >> >> Nicolas >> >> 2010/7/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >>> Levente /Eliot >>> >>> I noticed that >>> >>> $A hex on squeak >>> -> 41 >>> and in pharo >>> -> '16r41' >>> >>> I would like to have both consistent what do you think to have >>> >>> $A hex >>> -> '16r41' >>> >>> $A printStringHex >>> -> '41' >>> >>> like that this is consistent with the behavior on integer. >>> Eliot I saw that to change the behavior on characters and I would like to >>> know why. >>> I thought that it was for debugging purpose. >>> >>> Stef >>> >>> >>> >>> _______________________________________________ >>> 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

July 21, 2010

Re: [Pharo-project] about hex

by StÃ©phane Ducasse

On Jul 21, 2010, at 6:49 PM, Nicolas Cellier wrote: > I don't think Eliot changed that, he only changed Integer>>hex... No he did http://code.google.com/p/pharo/issues/detail?id=2705 Item was changed: ----- Method: Character>>hex (in category 'printing') ----- hex + ^value printStringBase: 16! - ^value hex! > It seems that every implementation of hex did avoid to print the radix in Squeak 3.10. Was it intentional ? > > Anyway, it will be hard to reach homogeneity because: > Integer>>hex should print the radix for VMMaker compatibility > ByteArray>>hex shouldn't for cypto compatibility but crypto could use printStringHex so yes we can reach it. > > Nicolas > > 2010/7/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Levente /Eliot > > I noticed that > > $A hex on squeak > -> 41 > and in pharo > -> '16r41' > > I would like to have both consistent what do you think to have > > $A hex > -> '16r41' > > $A printStringHex > -> '41' > > like that this is consistent with the behavior on integer. > Eliot I saw that to change the behavior on characters and I would like to know why. > I thought that it was for debugging purpose. > > Stef > > > > _______________________________________________ > 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

July 21, 2010