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

[Pharo-project] Parrot VM

by Miguel Enrique CobÃ¡ Martinez

Parrot has just been released: http://www.parrot.org/news/2010/Parrot-2.0.0 I would like to know, from the VM experts from the community, if this VM can be used to run Smalltalk. The site says that "Parrot is a virtual machine aimed at running all dynamic languages.". but I don't know anything about VM so this sounds to me a bit like black magic. Is there something in the squeak vm that is specific to the way smalltalk works or a generic virtual machine (maybe with a upper layer understanding Smalltalk specifics) can be used. Thanks for the answers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 20, 2010

Re: [Pharo-project] New profiler for Pharo: tester wanted!

by Miguel Enrique CobÃ¡ Martinez

El mar, 19-01-2010 a las 22:03 -0300, Alexandre Bergel escribiÃ³: > Dear List, > > Over the last few months I put some effort on a new profiler for > Pharo. It has been used on a number of projects. Time has come to > share it with you. > To install it, just doit the following expression in a workspace > (Mondrian will also be installed): > -=-=-=-=-=-=-=-=-=-=-=-= > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSpy'; > load. > (Smalltalk at: #ConfigurationOfSpy) perform: #loadDefault > -=-=-=-=-=-=-=-=-=-=-=-= I tried it in a PharoCore 1.0 10506 and I get a lot of deprecation warnings for gofer addPackage:, addVersion: The method Gofer addVersion: has been deprecated. Instead of #addVersion: simply use #version: Select Proceed to continue, or close this window to cancel the operation. I pressed proceed and then I got: MetacelloGoferPackage(Object)>>doesNotUnderstand: #setName. Is this for 1.0, what version? Cheers > > To invoke the profiler, use the following template: > ProfilingPackageSpy viewProfiling: [ "YOUR CODE" ] inPackage: > 'YourPackageName' > ProfilingPackageSpy viewProfiling: [ "YOUR CODE" ] > inPackagesMatching: 'PackageName*' > > Replace "YOUR CODE" by an expression. Some examples are provided in > the class ProfilingPackageSpy (method category 'example'). You can > find profilings of Mondrian, Glamour, Moose/CAnalyzer, O2. > The profiling of Mondrian looks like this: > -=-=-=-=-=-=-=-=-=-=-=-= > ProfilingPackageSpy > viewProfiling: [ > | view | > view := MOViewRenderer new. > view nodes: (1 to: 100) forEach: [:each | view nodes: (1 to: 100)]. > view root applyLayout > ] > inPackage: 'Mondrian' > -=-=-=-=-=-=-=-=-=-=-=-= > > There are two things you should keep in mind: > - "YOUR CODE" will be executed twice. The first time with message > Tally, then the second time with the full instrumentation. The second > execution should not be impacted by the first execution. > - You cannot instrument the whole image. I need more time to make this > happens. Therefore, you cannot provide '*' to inPackagesMatching: > > How to read the picture: > - big rectangle are classes > - edges represent class inheritance > - inner rectangles are methods: > * height = total time that the method has been executed > * width = number of time the method has been executed > * color = number of different receiver: white = the method has > been executed on 1 receiver. black = many receivers > > You can do a right-click on a method, and select viewInvocation. This > opens a second view that show the execution flow. A different mapping > of metrics is used: > - rectangle = methods > - edges = invocation (upper invokes below) > - gray color = method that always return 'self'. It corresponds to > void methods in Java or C++. It is therefore likely that the method > performs a side effect > - yellow color = method that always returns the same value for a > particular object > - width and height are as in the first visualization > > Keep in mind that you mind encounter a freeze of your image if you > instrument sensitive methods. > > I would be sincerely delighted to have experience report on this. > > Regards, > Alexandre > > -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 20, 2010

Re: [Pharo-project] Question about O2 dependencies

by Serge Stinckwich

Very interesting explanations indeed ! What would be nice is to have similar functionalities than GitHub for SqueakSource and more community aspects. 2010/1/20 Lukas Renggli <renggli(a)gmail.com>: > 2010/1/19 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >> >> On Tue, Jan 19, 2010 at 2:33 PM, David Roethlisberger >> <roethlis(a)iam.unibe.ch> wrote: >>> >>>>> Ok. Good. Right now, the Pharo community decided to use Lukas' >>>>> repository instead of Colin's one, but I guess it can be merged. Lukas ? >>> >>>> I find it unfriendly to merge into a foreign repository -- pull, fork and >>>> merge in your own repository. And eventually ask the maintainer to merge the >>>> code. >>> >>> I'm confused. What is the right process to update OB for Pharo now? In >>> Pharo-dev, as far as I see, OB is still taken from Colin's repo. Is this >>> gonna change now? Where should I commit a patch to OB now, to Colin's, to >>> Lukas' repo, somewhere else? >>> >>> Maybe best would be to have a non-personal repo on squeaksource which can >>> be used by all OB developers and from where Pharo takes the code? >>> >>> David >> >> I am confused too. Actually, this is exactly what I asked when people >> suggested to use Lukas' OB. > > Public code repositories do not work. I learned that with Seaside, and > we all saw that in all its ugliness with OmniBrowser. > > If this is a popular project in a public repository people will commit > changes to that repository. Some of the committed changes are ... > > - untested > - break existing tests > - break the architecture > - break other code > - put into the wrong package > - only working for the committer > - badly formatted or commented > - depend on non-existing code > - ... > > Now, if nobody constantly observes that repository and cleans it up, > you have an enormous mess. There are basically dozens of forks and > nobody knows what works, what is broken, what is official, what to > load, what to use, where to continue with development, etc. > > And that's not even the end of it. The next thing that happens is that > people start to merge: so random versions with random changes are > merged in a random order. As a result the problems and bugs multiply. > > After I saw GitHub, I realized that in the open-source world only > read-only code repositories work. The cool thing is that Monticello > and Git have a very similar model, so we just have to adapt their > process: > > - Every open-source project has a public read-only repository. Only > core contributes that trust each other can commit into this > repository. > > - If I want to change something, submit a bug-fix, or an enhancement I > simply fork the complete code base and commit it into my own > repository. > > - As a nice open-source contributor I ask one of the official > maintainers to merge my changes by pointing them to my repository: > > Â Â - If they like the changes, they will merge them into the official > repository. > > Â Â - If they don't like the changes, that's fine too. I have my own > repository and can use the code in there. > > That's it. It is simple and works really well. > > That's why my OB repository is read-only. I know that the code in > there passes all tests and that it does exactly what I want. Please > fork it, improve it, fix things, etc. If I learn about the changes and > if I like them I will merge them (that's what I did with some of the > O2 code). I do not commit my changes to Colin's repository though, if > he wants the code he can pull it (that's what he did in the past too). > > 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 > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Jan. 20, 2010

Re: [Pharo-project] Question on recursive structures

by Tudor Girba

Ohh, I guess I should go to sleep :). Doru On 20 Jan 2010, at 03:18, Serge Stinckwich wrote: > 2010/1/20 Tudor Girba <tudor.girba(a)gmail.com>: >> Hi, >> >> You can force an interrupt by CMD+i or CTRL+i (depending on the >> platform). > > This is not 'i' but '.' (period). > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Presenting is storytelling."

Jan. 20, 2010

Re: [Pharo-project] Question on recursive structures

by Serge Stinckwich

2010/1/20 Tudor Girba <tudor.girba(a)gmail.com>: > Hi, > > You can force an interrupt by CMD+i or CTRL+i (depending on the > platform). This is not 'i' but '.' (period). -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Jan. 20, 2010

[Pharo-project] Beta Testing

by Michael Litchard

Hi, I'm running NetBSD-current on AMD 64 bit. If that's useful to you I'd like to be a beta tester. Michael Litchard

Jan. 20, 2010

[Pharo-project] New profiler for Pharo: tester wanted!

by Alexandre Bergel

Dear List, Over the last few months I put some effort on a new profiler for Pharo. It has been used on a number of projects. Time has come to share it with you. To install it, just doit the following expression in a workspace (Mondrian will also be installed): -=-=-=-=-=-=-=-=-=-=-=-= Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSpy'; load. (Smalltalk at: #ConfigurationOfSpy) perform: #loadDefault -=-=-=-=-=-=-=-=-=-=-=-= To invoke the profiler, use the following template: ProfilingPackageSpy viewProfiling: [ "YOUR CODE" ] inPackage: 'YourPackageName' ProfilingPackageSpy viewProfiling: [ "YOUR CODE" ] inPackagesMatching: 'PackageName*' Replace "YOUR CODE" by an expression. Some examples are provided in the class ProfilingPackageSpy (method category 'example'). You can find profilings of Mondrian, Glamour, Moose/CAnalyzer, O2. The profiling of Mondrian looks like this: -=-=-=-=-=-=-=-=-=-=-=-= ProfilingPackageSpy viewProfiling: [ | view | view := MOViewRenderer new. view nodes: (1 to: 100) forEach: [:each | view nodes: (1 to: 100)]. view root applyLayout ] inPackage: 'Mondrian' -=-=-=-=-=-=-=-=-=-=-=-= There are two things you should keep in mind: - "YOUR CODE" will be executed twice. The first time with message Tally, then the second time with the full instrumentation. The second execution should not be impacted by the first execution. - You cannot instrument the whole image. I need more time to make this happens. Therefore, you cannot provide '*' to inPackagesMatching: How to read the picture: - big rectangle are classes - edges represent class inheritance - inner rectangles are methods: * height = total time that the method has been executed * width = number of time the method has been executed * color = number of different receiver: white = the method has been executed on 1 receiver. black = many receivers You can do a right-click on a method, and select viewInvocation. This opens a second view that show the execution flow. A different mapping of metrics is used: - rectangle = methods - edges = invocation (upper invokes below) - gray color = method that always return 'self'. It corresponds to void methods in Java or C++. It is therefore likely that the method performs a side effect - yellow color = method that always returns the same value for a particular object - width and height are as in the first visualization Keep in mind that you mind encounter a freeze of your image if you instrument sensitive methods. I would be sincerely delighted to have experience report on this. Regards, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2010

Re: [Pharo-project] Search in Pharo (and other Smalltalkices) what is out there?

by Adrian Kuhn

Mariano Martinez Peck <marianopeck@...> writes: > MessageNames ? Awesome, did not know that one, thanks! --AA

Jan. 20, 2010

Re: [Pharo-project] Question on recursive structures

by Schwab,Wilhelm K

Try alt (or control)-period ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Viktor Kerkez Sent: Tuesday, January 19, 2010 7:53 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Question on recursive structures I tried that first, but it doesn't work :( I'm using Pharo on Linux (Ubuntu). On Wed, Jan 20, 2010 at 1:47 AM, Tudor Girba <tudor.girba(a)gmail.com<mailto:tudor.girba@gmail.com>> wrote: Hi, You can force an interrupt by CMD+i or CTRL+i (depending on the platform). Cheers, Doru On 20 Jan 2010, at 01:44, Viktor Kerkez wrote: Hi, Since this is my first post on the list, first I want to thank you all for the great job you're doing on Pharo :) It was a real revelation when I discovered it :) Now to the question: I'm reading the Pharo by Example, and came to this part: The problem with deepCopy is that it will not terminate when applied to a mutually recursive structure: a1 := { 'harry' }. a2 := { a1 }. a1 at: 1 put: a2. a1 deepCopy â! ... does not terminate! (Pharo actually get stuck at the step: a1 at: 1 put: a2. but that's not the question :) ) 1. Isn't this behaviour (the complete environment get stuck and there is no way to unfreeze it) considered a bug? I mean the environment shouldn't let you shoot yourself in the foot (at least not so easily). Actually the same behaviour can be created just doing: [true] whileTrue: []... 2. Shouldn't Pharo recognize recursive structures in some way? I'm asking because I'm coming from a Python world, which is very similar to smalltalk in some manners and I'm trying to make a big picture comparison in my head. 1. I know that this doesn't really compares to Pharo which is a graphical environment, but in python you can always hit Ctrl-C and break the statements that block... >>> while True: ... pass ... ^CTraceback (most recent call last): File "<stdin>", line 1, in <module> KeyboardInterrupt >>> Shouldn't the UI thread always be responsive? 2. And Python recognizes recursive structures: >>> a = [] >>> a [] >>> a.append(5 ... KeyboardInterrupt >>> a = [] >>> a [] >>> a.append(5) >>> a [5] >>> a.append(a) >>> a [5, [...]] >>> a[0] 5 >>> a[1] [5, [...]] >>> a[1][1][1][1][0] 5 >>> Don't get me wrong, I'm not trying to start a language war :) I wouldn't got to page 171 if I'm not really interested in Smalltalk :-D I'm just trying to get a clearer vision if these are some things that are there for some reason (design decision), or they are just not yet implemented, or they cannot be implemented for some other reasons? Thank you in advance for your time :), Viktor _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com<http://www.tudorgirba.com> "Every now and then stop and ask yourself if the war you're fighting is the right one."

Jan. 20, 2010

Re: [Pharo-project] Question on recursive structures

by Viktor Kerkez

I tried that first, but it doesn't work :( I'm using Pharo on Linux (Ubuntu). On Wed, Jan 20, 2010 at 1:47 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > You can force an interrupt by CMD+i or CTRL+i (depending on the platform). > > Cheers, > Doru > > > > On 20 Jan 2010, at 01:44, Viktor Kerkez wrote: > > Hi, >> >> Since this is my first post on the list, first I want to thank you all for >> the great job you're doing on Pharo :) It was a real revelation when I >> discovered it :) >> >> Now to the question: >> >> I'm reading the Pharo by Example, and came to this part: >> >> The problem with deepCopy is that it will not terminate when applied to a >> mutually recursive structure: >> a1 := { 'harry' }. >> a2 := { a1 }. >> a1 at: 1 put: a2. >> a1 deepCopy â! ... does not terminate! >> >> (Pharo actually get stuck at the step: a1 at: 1 put: a2. but that's not >> the question :) ) >> >> 1. Isn't this behaviour (the complete environment get stuck and there is >> no way to unfreeze it) considered a bug? I mean the environment shouldn't >> let you shoot yourself in the foot (at least not so easily). Actually the >> same behaviour can be created just doing: [true] whileTrue: []... >> >> 2. Shouldn't Pharo recognize recursive structures in some way? >> >> >> I'm asking because I'm coming from a Python world, which is very similar >> to smalltalk in some manners and I'm trying to make a big picture comparison >> in my head. >> >> 1. I know that this doesn't really compares to Pharo which is a graphical >> environment, but in python you can always hit Ctrl-C and break the >> statements that block... >> >> >>> while True: >> ... pass >> ... >> ^CTraceback (most recent call last): >> File "<stdin>", line 1, in <module> >> KeyboardInterrupt >> >>> >> >> Shouldn't the UI thread always be responsive? >> >> 2. And Python recognizes recursive structures: >> >> >>> a = [] >> >>> a >> [] >> >>> a.append(5 >> ... >> KeyboardInterrupt >> >>> a = [] >> >>> a >> [] >> >>> a.append(5) >> >>> a >> [5] >> >>> a.append(a) >> >>> a >> [5, [...]] >> >>> a[0] >> 5 >> >>> a[1] >> [5, [...]] >> >>> a[1][1][1][1][0] >> 5 >> >>> >> >> >> Don't get me wrong, I'm not trying to start a language war :) I wouldn't >> got to page 171 if I'm not really interested in Smalltalk :-D I'm just >> trying to get a clearer vision if these are some things that are there for >> some reason (design decision), or they are just not yet implemented, or they >> cannot be implemented for some other reasons? >> >> Thank you in advance for your time :), >> Viktor >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > www.tudorgirba.com > > "Every now and then stop and ask yourself if the war you're fighting is the > right one." > > > >

Jan. 20, 2010