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

Re: [Pharo-project] [COTDC] 4 - RecategorizedEvent

by Benjamin

I'm the event sent by the system when a method or a class is recategorized. To retrieve information, you can access to: item: the CompiledMethod or the class recategorized itemKind: #method for a method, #class for a class environment: aDictionary with new information for a method: - #class: the class of the method (it hasn't changed) - #protocol: the new category of the method - #selector: the selector of the method (it hasn't changed) for a class: - #category: the new category oldCategory: the category where the item was formerly categorized Ben On Feb 7, 2011, at 7:35 PM, Esteban Lorenzano wrote: > Also, AbstractEvent is not commented: > > I'm a generic event raised by the system (SystemChangeNotifier) when anything (both classes or methods) changes in the system. > Each one of my children represents a specific kind of event the system can notify. > > Now I will soon fade away and be replaced by announcements. > > (not a lot imaginative, but works :)) > > El 07/02/2011, a las 3:25p.m., StÃ©phane Ducasse escribiÃ³: > >> I'm an event raised by the system (SystemChangeNotifier) when a class or a method changed its category. The way to create my instances is the following: >> >> >> (RecategorizedEvent >> method: (aClass compiledMethodAt: selector ifAbsent: [nil]) >> selector: selector >> protocol: newCategory >> class: aClass >> oldProtocol: oldCategory) >> >> >> (RecategorizedEvent >> class: aClass >> category: newCategory >> oldCategory: oldCategory) >> >> Now I will soon fade away and be replaced by announcements. >> >> >> >> >> >> On Feb 7, 2011, at 6:25 PM, laurent laffont wrote: >> >>> Comment Of The Day Contest - One Day One Comment >>> Rules: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). >>> >>> >>> Today: RecategorizedEvent >>> >>> >>> Laurent >> >> > >

Feb. 8, 2011

Re: [Pharo-project] Status of Alien

by Schwab,Wilhelm K

Torsten, I have been under the impression that it has never worked on Linux - it would be great to be wrong on that. Does anyone have Alien on Linux waiting for someone to try it? One thing slowing my search for FFI/Alien improvements has been that I was initially dependent on some vm modifications that I made. Some off-line correspondence with Dave Lewis and the benefit of some time might have yielded a solution that will let me return to stock vms. FFI has generally worked for me. I am doing a horrible job of handling double arrays, but I am at least able to use them. My "solution" makes assumptions about byte order and I have declare double* as void*. There was mention of extending FFI with callbacks. Given that capability, the only thing missing would then to be make calls on OS threads to avoid blocking the image (but blocking the calling Smalltalk Process for the duration of the call). Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Torsten Bergmann [astares(a)gmx.de] Sent: Tuesday, February 08, 2011 4:04 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Status of Alien What is the status of Alien. According to http://bugs.squeak.org/view.php?id=7475 there is no one who confirmed it working on Linux. Any news here? Any ideas on FFI/Alien successor? Thanks T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Feb. 8, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #21 on issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 In the Pharo 1.2 12324, there is no shouting either in the Debugger or in the Workspace.

Feb. 8, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #20 on issue 3583 by hisnamei...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 There is no shouting, or the shouting is badly done ?

Feb. 8, 2011

[Pharo-project] Fwd: [squeak-dev] Squeak vs Python "smack down"

by StÃ©phane Ducasse

From: GÃ¶ran Krampe <goran(a)krampe.se> > Date: February 8, 2011 12:01:48 AM GMT+01:00 > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org>, Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > Subject: [squeak-dev] Squeak vs Python "smack down" > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > Hi folks! > > Since we are on the verge of 4.2, and we have a brand new Cog VM to play with I felt like dusting off my old Pystone port to Squeak - Sqystone, which I wrote back in 2004. > > At that time Squeak was around 5 times faster than CPython. How do we stack up today? Yeah, I know - hardly a good benchmark, they all lie etc etc. :) > > I am using Ubuntu 10.10 on a corei7, so this is running on a 64 bit CPU. > > > Cog! > ==== > Squeak 4.2-10966 (soon to be released) + latest Cog r2361 (binary download): > Pystone(1.1) time for 50000 passes = 0.06 > This machine benchmarks at 833333.3 pystones/second > > NOTE: AFAICT running with more passes does not improve it. Also, not sure if I could get more out of this if I built from source on my box. > > > Regular Squeak > ============== > Squeak 4.2-10966 (soon to be released) + regular Squeak VM 4.4.7-2357 (built from src): > Pystone(1.1) time for 50000 passes = 0.503 > This machine benchmarks at 99403.6 pystones/second > > > Regular CPython > =============== > CPython 3.1.2 (newest in Ubuntu Meerkat, minimal): > gokr@quigon:/usr/lib/python3.1/test$ python3.1 pystone.py > Pystone(1.1) time for 50000 passes = 0.57 > This machine benchmarks at 87719.3 pystones/second > > NOTE: 3.2 is reportedly a teeny bit faster. Also not built from source. > > > Pypy 1.4 > ======== > wget http://pypy.org/download/pypy-1.4.1-linux64.tar.bz2 > gokr@quigon:~/python/pypy-1.4.1-linux64$ ./bin/pypy ./lib-python/2.5.2/test/pystone.py > Pystone(1.1) time for 50000 passes = 0.15 > This machine benchmarks at 333333 pystones/second > gokr@quigon:~/python/pypy-1.4.1-linux64$ ./bin/pypy ./lib-python/2.5.2/test/pystone.py 5000000 > Pystone(1.1) time for 5000000 passes = 4.8 > This machine benchmarks at 1.04167e+06 pystones/second > > NOTE: Also not built from source. Here we run pystone a second time with 100x more loops and get a substantially better number. > > > Shedskin 0.7 > ============ > sudo apt-get install g++ libpcre3-dev libgc-dev python-dev > sudo dpkg -i shedskin_0.7_all.deb > wget http://shedskin.googlecode.com/files/shedskin-examples-0.7.tgz > shedskin pystone.py > gokr@quigon:~/python/shedskin-examples-0.7$ make > g++ -O2 -march=native -fomit-frame-pointer -Wno-deprecated -I. -I/usr/share/shedskin/lib /usr/share/shedskin/lib/builtin.cpp pystone.cpp /usr/share/shedskin/lib/time.cpp /usr/share/shedskin/lib/re.cpp -lgc -lpcre -o pystone > gokr@quigon:~/python/gokr@quigon:~/python/shedskin-examples-0.7$ ls -la pystone* > -rwxr-xr-x 1 gokr gokr 297329 2011-02-07 23:01 pystone > -rw-r--r-- 1 gokr gokr 9193 2011-02-07 23:00 pystone.cpp > -rw-r--r-- 1 gokr gokr 1893 2011-02-07 23:00 pystone.hpp > -rw-r--r-- 1 gokr gokr 5774 2010-12-11 11:40 pystone.py > gokr@quigon:~/python/shedskin-examples-0.7$ ./pystone > This machine benchmarks at 2500000.000000 pystones/second > > NOTE: I am wondering a bit about this. It tells the same whatever loops I give it... But ok, perhaps it is all fine. > > > Summary > ======= > > - The regular Squeak VM has not been overrun by CPython in these 6 years time. When I wrote Sqystone Squeak was 5x faster IIRC (can't find the post anymore). Now they are equal more or less, Squeak still a teeny bit faster. > > - Cog is brutally fast on this one. Compared to CPython and regular Squeak almost 10x faster. > > - Pypy is about 20% faster than Cog if given enough time to actually start jitting. Cool for the Pypy project! And cool that they aren't that much faster than Cog. :) > > - Shedskin is the "state of the art" of statically compiling Python via C++ using type inferencing etc etc - so I hear. It is said to be faster than Cython and Psyco. It ends up beating Cog, but "only" by a factor of 3x. I say "only" because that seems pretty good to me given that Cog is a JIT and still pretty young and that Shedskin can only run a subset of Python. Rerunning Cog and CPython too with 5000000 loops didn't change the numbers much, but for Shedskin it turns out more proper: gokr@quigon:~/python/shedskin-examples-0.7$ ./pystone This machine benchmarks at 3546099.290780 pystones/second 50000 loops was just too small. So in fact it is about 4.4x faster than Cog. And yes, the ported pystone for shedskin had the loops hard coded. :) regards, GÃ¶ran

Feb. 8, 2011

[Pharo-project] Fwd: Canvas >>draw: anObject

by StÃ©phane Ducasse

Begin forwarded message: > From: "juan(a)jvuletich.org" <juan(a)jvuletich.org> > Date: February 8, 2011 2:25:33 AM GMT+01:00 > To: stephane.ducasse(a)inria.fr, juan(a)jvuletich.org > Subject: RE: Canvas >>draw: anObject > Reply-To: juan(a)jvuletich.org > > (Please forward to Pharo, it seems I can't send to it from webmail) > > The difference is not really important. If you have a Morph that draws > outside > its bounds (no morph should ever do that) the version in SM (I guess it is > the > original Squeak code), will clip. The Pharo version won't. That means that > such > a morph would leave a trail if moved around. > > For example, I just added: > aCanvas fillRectangle: (bounds translateBy: 10) fillStyle: Color red. > at the start of EllipseMorph>>drawOn: , and modified #draw: to be like in > Pharo. > Then you open an ellipse, and when you move it around it leaves red garbage. > > If morphs work properly, then it makes no difference. Maybe a very slight > performance difference, but not sure. > > HTH. > > Cheers, > Juan Vuletich > > Original Message: > ----------------- > From: StÃ©phane Ducasse stephane.ducasse(a)inria.fr > Date: Mon, 7 Feb 2011 22:41:08 +0100 > To: juan(a)jvuletich.org, Pharo-project(a)lists.gforge.inria.fr > Subject: Canvas >>draw: anObject > > > Canvas>>draw: anObject > ^anObject drawOn: self > > > Now in SM we got > > SMxCanvas>>draw: anObject > ^self clipBy: anObject bounds during: [ :c | anObject drawOn: c] > > and I'm wondering what is the exact difference. > Any idea? > > Stef > > > -------------------------------------------------------------------- > mail2web.com â Enhanced email for the mobile individual based on MicrosoftÂ® > Exchange - http://link.mail2web.com/Personal/EnhancedEmail > >

Feb. 8, 2011

Re: [Pharo-project] Canvas>>render:

by StÃ©phane Ducasse

Yes this was my impression too. Stef On Feb 8, 2011, at 12:47 AM, Igor Stasenko wrote: > it looks like a double-dispatch pattern, same as draw/drawOn: . > Its of course completely useless unless you have objects capable of rendering. > > Also, i'm not sure that crossing 2D -> 3D could be done so easily and > painless as this method proposing.. > and i'm not sure that mixing them is a good idea: > - original canvas operating at bitmap level > - 3d canvas operating at triangle/mesh level(s) > > > On 7 February 2011 22:36, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi >> >> I have the impression that we could remove this method and friends since it definition on FormCanvas is >> >> render: anObject >> "Do some 3D operations with the object if possible" >> ^self asBalloonCanvas render: anObject >> >> But BalloonCanvas does not implement render: >> >> and >> Canvas>>render: anObject >> "Do some 3D operations with the object if possible" >> >> is a nop. >> >> Stef >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Feb. 8, 2011

Re: [Pharo-project] Canvas >>draw: anObject

by StÃ©phane Ducasse

Yes now apparently even if I draw outside the bounds they are clipped in pharo too. I have to check how. On Feb 8, 2011, at 12:51 AM, Igor Stasenko wrote: > On 7 February 2011 22:41, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Canvas>>draw: anObject >> ^anObject drawOn: self >> >> >> Now in SM we got >> >> SMxCanvas>>draw: anObject >> ^self clipBy: anObject bounds during: [ :c | anObject drawOn: c] >> >> and I'm wondering what is the exact difference. >> Any idea? >> > > yes, > SMxCanvas ensures that not matter what happens, a morph cannot draw > outside of its declared bounds. > Which usually should not happen anyways.. so it looks like an > additional rule enforcement. > > > >> Stef >> > > > -- > Best regards, > Igor Stasenko AKA sig. >

Feb. 8, 2011

Re: [Pharo-project] Our response to JS proxy API + Cog regression

by StÃ©phane Ducasse

Thanks because this is a really really really good hook. Stef > > There is only one thing, which not OK with it: > - Cog having a regression comparing to Squeak VM. > Its not handling #cannotInterpret: message correctly. > > Yes, I didn't implement the cannotInterpret: hook for Cog fully. I'll take a look at this soon. > > cheers, > Eliot > > > [1] research.google.com/pubs/archive/36574.pdf > [2] http://code.google.com/p/pharo/issues/detail?id=3648 > > -- > Best regards, > Igor Stasenko AKA sig. >

Feb. 8, 2011

Re: [Pharo-project] [COTDC] 4 - RecategorizedEvent

by laurent laffont

On Tue, Feb 8, 2011 at 10:31 AM, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > > > Also, AbstractEvent is not commented: > > and all subclasses... may be not needed to comment them all (except > examples maybe - but if they vanish... :) )... all are in > system-change-notification category > "see AbstractEvent" is a valid comment. Laurent. > > > > > > > > > I'm a generic event raised by the system (SystemChangeNotifier) when > anything (both classes or methods) changes in the system. > > Each one of my children represents a specific kind of event the system > can notify. > > > > Now I will soon fade away and be replaced by announcements. > > > > (not a lot imaginative, but works :)) > > > > El 07/02/2011, a las 3:25p.m., StÃ©phane Ducasse escribiÃ³: > > > >> I'm an event raised by the system (SystemChangeNotifier) when a class or > a method changed its category. The way to create my instances is the > following: > >> > >> > >> (RecategorizedEvent > >> method: (aClass compiledMethodAt: selector ifAbsent: [nil]) > >> selector: selector > >> protocol: newCategory > >> class: aClass > >> oldProtocol: oldCategory) > >> > >> > >> (RecategorizedEvent > >> class: aClass > >> category: newCategory > >> oldCategory: oldCategory) > >> > >> Now I will soon fade away and be replaced by announcements. > >> > >> > >> > >> > >> > >> On Feb 7, 2011, at 6:25 PM, laurent laffont wrote: > >> > >>> Comment Of The Day Contest - One Day One Comment > >>> Rules: Each day a not commented class is elected. Each day the best > comment will be integrated with name of the author(s). > >>> > >>> > >>> Today: RecategorizedEvent > >>> > >>> > >>> Laurent > >> > >> > > > > > > >

Feb. 8, 2011