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

Re: [Pharo-project] Meanwhile, at another vm

by Stefan Marr

Hi: On 13 Apr 2011, at 16:44, Mariano Martinez Peck wrote: > > "Running on the JVM" and "Running on the JVM" are two completely different things. > Here seems to be the same > > 'Running on the JVM' = 'Running on the JVM' -> true > > ehehhe I guess you forgot to change something or I am so stupid to understand... Sorry, that was on purpose. 'Running on the JVM' is just a useless term. Potato shows how to implement an interpreter in Java that runs on top of the JVM. With some minor adaptations it would also be able to run Pharo. But the question is, how useful would that be. With that model, it is not directly possible to exploit JVM mechanism like threads. It is basically identical to the SqueakVM with just exchanging C for Java. Even compiling Smalltalk to Java bytecode does not get you closer to leveraging the JVM. It would be 'just' Cog, with JVM bytecodes as a target instead of x86. You get speed, but you do not really get closer to use the JVM platform. Best regards Stefan > > Just a reminder: > http://news.squeak.org/2008/07/07/potato-version-of-jsqueak-from-hpi/ PS: It would be awesome if my mail client would be able to quote your mail correctly. -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

April 13, 2011

Re: [Pharo-project] Play and crash

by laurent laffont

Cool ! Thank you all ! Have put this at http://magaloma.blogspot.com/2011/04/polymorph-counter-example.html http://magaloma.blogspot.com/2011/04/petite-horloge-revisited.html Laurent. On Wed, Apr 13, 2011 at 4:25 PM, Henrik Sperre Johansen < henrik.s.johansen(a)veloxit.no> wrote: > On 13.04.2011 16:16, laurent laffont wrote: > >> This works: >> >> counter := Class new >> superclass: Object; >> addInstVarNamed: 'counter'; >> compile: 'initialize >> counter := 0'; >> compile: 'counterString >> ^ counter asString'; >> compile: 'increment >> counter := counter + 1. >> self changed:#counterString'; >> compile: 'decrement >> counter := counter - 1. >> self changed:#counterString'; >> new. >> >> (UITheme builder newColumn: { >> UITheme builder newLabelFor: counter getLabel: #counterString getEnabled: >> nil. >> UITheme builder newRow: { >> UITheme builder newButtonFor: counter action: #increment label: '+' >> help: nil. >> UITheme builder newButtonFor: counter action: #decrement label: '-' >> help: nil. >> } >> }) openInWindowLabeled: 'Counter example'. >> >> >> >> This one crashes the VM (tried on PharoOneClick 1.2 OSX, Cog and StackVM): >> >> (Class new >> superclass: StringMorph; >> compile: 'step self contents: Time now printString'; >> new) >> openCenteredInWorld >> >> >> >> Any idea ? >> > > http://forum.world.st/test-crashing-the-cog-vm-td3393032.html > Answer in first reply :) > > Cheers, > Henry > >

April 13, 2011

[Pharo-project] isHealthy

by StÃ©phane Ducasse

Hi igor this is strange I have a dictionary whose array contains nil and still isHealthy returns true. can an array of a dictionary contains nil? Stef

April 13, 2011

Re: [Pharo-project] Meanwhile, at another vm

by Mariano Martinez Peck

On Wed, Apr 13, 2011 at 4:21 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: > > On 13 Apr 2011, at 09:32, Philippe Marschall wrote: > > Probably not. I mean you all the code relying on primitives, all the > > code relying on ByteString having the same memory layout as ByteArray, > > all the code relying on the scheduler being non-preemptive, all the > > code relying on #become: and so forth. > > "Running on the JVM" and "Running on the JVM" are two completely different > things. > > Here seems to be the same 'Running on the JVM' = 'Running on the JVM' -> true ehehhe I guess you forgot to change something or I am so stupid to understand... > Just a reminder: > http://news.squeak.org/2008/07/07/potato-version-of-jsqueak-from-hpi/ > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > > -- Mariano http://marianopeck.wordpress.com

April 13, 2011

Re: [Pharo-project] Play and crash

by Henrik Sperre Johansen

On 13.04.2011 16:16, laurent laffont wrote: > This works: > > counter := Class new > superclass: Object; > addInstVarNamed: 'counter'; > compile: 'initialize > counter := 0'; > compile: 'counterString > ^ counter asString'; > compile: 'increment > counter := counter + 1. > self changed:#counterString'; > compile: 'decrement > counter := counter - 1. > self changed:#counterString'; > new. > > (UITheme builder newColumn: { > UITheme builder newLabelFor: counter getLabel: #counterString > getEnabled: nil. > UITheme builder newRow: { > UITheme builder newButtonFor: counter action: #increment label: > '+' help: nil. > UITheme builder newButtonFor: counter action: #decrement label: > '-' help: nil. > } > }) openInWindowLabeled: 'Counter example'. > > > > This one crashes the VM (tried on PharoOneClick 1.2 OSX, Cog and StackVM): > > (Class new > superclass: StringMorph; > compile: 'step self contents: Time now printString'; > new) > openCenteredInWorld > > > > Any idea ? http://forum.world.st/test-crashing-the-cog-vm-td3393032.html Answer in first reply :) Cheers, Henry

April 13, 2011

Re: [Pharo-project] Play and crash

by Igor Stasenko

On 13 April 2011 16:16, laurent laffont <laurent.laffont(a)gmail.com> wrote: > This works: > counter := Class new > Â Â Â Â Â Â Â Â superclass: Object; > Â Â Â Â Â Â Â Â addInstVarNamed: 'counter'; > Â Â Â Â Â Â Â Â compile: 'initialize > Â Â Â Â Â Â Â Â Â Â Â Â Â Â counter := 0'; > Â Â Â Â Â Â Â Â compile: 'counterString > Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^ counter asString'; > Â Â Â Â Â Â Â Â compile: 'increment > Â Â Â Â Â Â Â Â Â Â Â Â Â Â counter := counter + 1. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â self changed:#counterString'; > Â Â Â Â Â Â Â Â compile: 'decrement > Â Â Â Â Â Â Â Â Â Â Â Â Â Â counter := counter - 1. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â self changed:#counterString'; > Â Â Â Â Â Â Â Â new. > (UITheme builder newColumn: { > Â Â UITheme builder newLabelFor: counter getLabel: #counterString getEnabled: > nil. > Â Â UITheme builder newRow: { > Â Â Â UITheme builder newButtonFor: counter action: #increment label: '+' > help: nil. > Â Â Â UITheme builder newButtonFor: counter action: #decrement label: '-' > help: nil. > Â Â } > }) openInWindowLabeled: 'Counter example'. > > > This one crashes the VM (tried on PharoOneClick 1.2 OSX, Cog and StackVM): > (Class new > Â Â superclass: StringMorph; > Â Â compile: 'step self contents: Time now printString'; > Â Â new) > Â Â Â openCenteredInWorld > > > Any idea ? > yes. because format of the class are not initialized properly. this one works: (Class new superclass: StringMorph; setFormat: StringMorph format; compile: 'step self contents: Time now printString'; new) openCenteredInWorld > > Laurent Laffont -Â @lolgzs > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > Developer group: http://cara74.seasidehosting.st > -- Best regards, Igor Stasenko AKA sig.

April 13, 2011

Re: [Pharo-project] Meanwhile, at another vm

by Stefan Marr

On 13 Apr 2011, at 09:32, Philippe Marschall wrote: > Probably not. I mean you all the code relying on primitives, all the > code relying on ByteString having the same memory layout as ByteArray, > all the code relying on the scheduler being non-preemptive, all the > code relying on #become: and so forth. "Running on the JVM" and "Running on the JVM" are two completely different things. Just a reminder: http://news.squeak.org/2008/07/07/potato-version-of-jsqueak-from-hpi/ -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #7 on issue 4003 by siguc...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 here the part of code which responsible for doing startup: self processStartUpList: resuming. resuming ifTrue: [ self recordStartupStamp ]. UIManager default onSnapshot: resuming. "Now it's time to raise an error" as you can see, the process list are ehmm.. processed before UIManager takes a control (and before switching to non-interactive mode). It means that if any startup procedure added by some arbitrary class will fail with error, it will end up using old UIManager, which could open a debugger window and waiting for user's interaction. From other side, im not sure it would be wise to switch UIManager before processing the startup list, because it in own turn could depend on startup of things like Delay etc.

April 13, 2011

[Pharo-project] Play and crash

by laurent laffont

This works: counter := Class new superclass: Object; addInstVarNamed: 'counter'; compile: 'initialize counter := 0'; compile: 'counterString ^ counter asString'; compile: 'increment counter := counter + 1. self changed:#counterString'; compile: 'decrement counter := counter - 1. self changed:#counterString'; new. (UITheme builder newColumn: { UITheme builder newLabelFor: counter getLabel: #counterString getEnabled: nil. UITheme builder newRow: { UITheme builder newButtonFor: counter action: #increment label: '+' help: nil. UITheme builder newButtonFor: counter action: #decrement label: '-' help: nil. } }) openInWindowLabeled: 'Counter example'. This one crashes the VM (tried on PharoOneClick 1.2 OSX, Cog and StackVM): (Class new superclass: StringMorph; compile: 'step self contents: Time now printString'; new) openCenteredInWorld Any idea ? Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

April 13, 2011

Re: [Pharo-project] Meanwhile, at another vm

by Philippe Marschall

On 04/13/2011 02:57 PM, StÃ©phane Ducasse wrote: > still this can always be interesting to learn your limit and dependencies. Sure, didn't make any judgments in any way. Just said I see some problems on the road. Cheers Philippe

April 13, 2011