- Pharo-dev - lists.pharo.org

Re: [Pharo-project] class message

by Mariano Martinez Peck

On Sat, May 26, 2012 at 8:36 PM, Milan Mimica <milan.mimica(a)gmail.com>wrote: > On 26 May 2012 20:32, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> >> >> On Sat, May 26, 2012 at 8:31 PM, Milan Mimica <milan.mimica(a)gmail.com>wrote: >> >>> Hello! >>> >>> What has changed in implementation "class" message in between Pharo 1.3 >>> and 1.4? Is it compiled inline now or something like that? >>> >> >> no, the other way around, now #class is NOT bytecoded, and therefore is >> managed as a normal message send. >> > > That is much better. Thanks! I like progress even if it breaks old code. > breaks? can you give us an example? beause it has to be something quite hacky or low level, has't it? > > > -- > Milan Mimica > http://sparklet.sf.net > -- Mariano http://marianopeck.wordpress.com

May 26, 2012

Re: [Pharo-project] class message

by StÃ©phane Ducasse

> > What has changed in implementation "class" message in between Pharo 1.3 and 1.4? Is it compiled inline now or something like that? > > no, the other way around, now #class is NOT bytecoded, and therefore is managed as a normal message send. > > That is much better. Thanks! I like progress even if it breaks old code. :) But we always try to minimize else we would go much faster and btw class should not break older code :) > > > -- > Milan Mimica > http://sparklet.sf.net

May 26, 2012

Re: [Pharo-project] class message

by Milan Mimica

On 26 May 2012 20:32, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Sat, May 26, 2012 at 8:31 PM, Milan Mimica <milan.mimica(a)gmail.com>wrote: > >> Hello! >> >> What has changed in implementation "class" message in between Pharo 1.3 >> and 1.4? Is it compiled inline now or something like that? >> > > no, the other way around, now #class is NOT bytecoded, and therefore is > managed as a normal message send. > That is much better. Thanks! I like progress even if it breaks old code. -- Milan Mimica http://sparklet.sf.net

May 26, 2012

Re: [Pharo-project] class message

by Mariano Martinez Peck

On Sat, May 26, 2012 at 8:31 PM, Milan Mimica <milan.mimica(a)gmail.com>wrote: > Hello! > > What has changed in implementation "class" message in between Pharo 1.3 > and 1.4? Is it compiled inline now or something like that? > no, the other way around, now #class is NOT bytecoded, and therefore is managed as a normal message send. > > > -- > Milan Mimica > http://sparklet.sf.net > -- Mariano http://marianopeck.wordpress.com

May 26, 2012

[Pharo-project] class message

by Milan Mimica

Hello! What has changed in implementation "class" message in between Pharo 1.3 and 1.4? Is it compiled inline now or something like that? -- Milan Mimica http://sparklet.sf.net

May 26, 2012

Re: [Pharo-project] RPackage problem with obsolete classes

by Mariano Martinez Peck

On Sat, May 26, 2012 at 3:02 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > This test illustrate the problem: > > testMethodPackageFromObsoleteClass > | pack method | > pack := self createNewPackageNamed: 'P1'. > foo := self createNewClassNamed: #FooForTest inPackage: pack. > foo compileSilently: 'bar ^42'. > method := foo>>#bar. > foo removeFromSystem. > self assert: (method packageFromOrganizer: pack organizer)equals: foo > package. > > > This seems to happen in non silent tests that > > - create a class/trait for test > - sends an announcement with a compiled method instance (like, method > recategorized) > - remove the class/trait because they are for test only :) > - then, since the announcements are handled asychronously, a method from > an obsolete category reaches somewhere, and RPackage explodes. > > This is *exactlly* the problem I faced when running Fuel tests in Pharo 2.0. I could have time to fix it, nor anyone else. Therefore, what I did is to realy fix Fuel to have ALL tests completly silent. And of course that fixed the problem. Nice that at least you could write a test :) -- Mariano http://marianopeck.wordpress.com

May 26, 2012

Re: [Pharo-project] [update 2.0] #20100

by Marcus Denker

We retract that update.... some strange error happens headless on macos. On May 26, 2012, at 4:17 PM, Marcus Denker wrote: > 20100 > ----- > > Issue 5964: WeakRegistry dictionary grows indefinitely large > http://code.google.com/p/pharo/issues/detail?id=5964 > -- > Marcus Denker -- http://marcusdenker.de > -- Marcus Denker -- http://marcusdenker.de

May 26, 2012

Re: [Pharo-project] Working directory

by David T. Lewis

On Sat, May 26, 2012 at 10:44:15AM +0200, Camillo Bruni wrote: > > On 2012-05-26, at 06:41, David T. Lewis wrote: > > > What is a "working directory"? And for that matter, what is a "directory"? > > These are concepts and metaphors that have been used in various ways by > > some (but not all) operating systems, and that do not automatically have > > a well defined meaning independent of those metaphors and operating systems. > > There is really no such thing as "current working directory" in Squeak/Pharo, > > so if you want to create such a concept you are free to do so in any way > > you please. > > well on all unix there is a very clear precise definition of it "getcwd()"! > and on all decent platforms there's a more or less clear notion of > what is a file and what is a directory? > > Talking about Pharo, which platforms do we target? > - Linux > - OS X > - Win You're right about that of course. I guess I just like to remind people that unix is not the only good operating system that has ever been invented, and that ideas like "files" are just part of a metaphor that was invented decades ago to help people relate their computer to something they already understood (a physical desk with a desktop and with file cabinets filled with folders that contained paper documents). With cell phones, tablets, and solid state storage it is quite possible that the ancient "desk with file cabinet" metaphors will become obsolete, so it is good to keep an open mind. > > maybe I am wrong, but I think we could assume a common denominator here? > (Using python and ruby yields to the same results AFAIK) I don't know. But OS X may well be an example of an environment that presents a file system view to the user that is different from the file system view at the unix file system or unix shell level. And Windows 7 appears to be trying to imitate OS X in that regard. If you implement a concept of "current working directory" in the image, you are free to define it in whatever way makes good sense. But there is no fundamental reason why you need to use a definition that matches the unix file system view (as reported by OSProcess). You might instead prefer to use a definition that matches what the OS X user expects to see in the finder, and maybe that is a different thing (I am not an OS X user, so apologies if I am getting this wrong). Dave

May 26, 2012

[Pharo-project] Pharo-2.0-Tests Â» 32,mac - Build # 100 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

May 26, 2012

[Pharo-project] Pharo-2.0-Tests Â» 32,mac - Build # 99 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

May 26, 2012