- Pharo-dev - lists.pharo.org

Re: [Pharo-project] cannot loadOBalpha in 10166 dev

by David RÃ¶thlisberger

> I can loadOBAlpha in a 10166dev 08.11.6 I also tested loadOBAlpha in a fresh pharo0.1-10166dev08.11.6 and it works fine too. So what is the exact problem you get? david

Nov. 26, 2008

[Pharo-project] mac carbon VM Squeak 3.8.20beta1U.app ships for testing.

by John M McIntosh

I've stuck a Squeak 3.8.20beta1U.app.zip file in my EXPERIMENTAL folder found via http://www.smalltalkconsulting.com/squeak.html This test VM contains the latest 32/64 bit integer fetch/set logic & fixes, Alien support and the Alien (IA32ABI) plugin, along with misc fixes to the VM consolidated by Tim and integrated into VMMaker by David T. Lewis in the last few months. If you want to explore Alien then you need this VM and it's plugin to continue. Hint if someone would like to run some benchmarks and compare Alien versus FFI calls that would be good. I note the Alien plugin is macintel only, no powerpc at this time (got funding?) -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Nov. 26, 2008

Re: [Pharo-project] cannot loadOBalpha in 10166 dev

by StÃ©phane Ducasse

to load the latest version. Stef On Nov 25, 2008, at 12:13 PM, Alexandre Bergel wrote: > I can load it in 10156 (non-dev), 10164 (non-dev). > I can loadOBAlpha in a 10166dev 08.11.6 > > But why would you want to load it in a dev edition? OB is already > included there. > > Alexandre > > On 25 Nov 2008, at 06:56, StÃ©phane Ducasse wrote: > >> Hi David >> >> I cannot load... >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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 >

Nov. 25, 2008

[Pharo-project] [ANN] Image for #10172

by Marcus Denker

https://gforge.inria.fr/frs/download.php/11596/Pharo0.1Core-10172.zip ChangeLog ========= update10165 Stef and Damien happily adding tests to Array, OrderedCollection, Set, Bag, String, Symbol, Dictionary based on traits TIncludesTest, TCloneTest, TCopyTest ------------------------------------------------------ update10166 Simon fixes to icons tests No author pop up ------------------------------------------------------ update10167 - clean more Preferences (Marcus Denker) - Scriptloader Seaside loading methods (Torsten Bergmann) - Postscript: (Preferences preferenceAt: #allowEtoyUserCustomEvents) changeInformee: nil changeSelector: nil. Preferences removePreference: #batchPenTrails. Preferences removePreference: #allowEtoyUserCustomEvents. Preferences removePreference: #automaticViewerPlacement. Preferences removePreference: #capitalizedReferences. Preferences removePreference: #fenceEnabled. Preferences removePreference: #keepTickingWhilePainting. Preferences removePreference: #tileTranslucentDrag. Preferences removePreference: #translationWithBabel. Preferences removePreference: #useButtonProprtiesToFire. Preferences removePreference: #alphabeticalProjectMenu. Preferences removePreference: #showAdvancedNavigatorButtons. Preferences removePreference: #ignoreStyleIfOnlyBold. Preferences removePreference: #propertySheetFromHalo. ------------------------------------------------------------ 10168-10172: FreeType ' ============== -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 25, 2008

Re: [Pharo-project] Wrapper bug (is ByteSurgeon the cause of it ?)

by Antoine Marot

Le 25-nov.-08 Ã 14:00, Marcus Denker a Ã©crit : > Very strage... I think in general it is not good to use the > doesNotUnderstand trick so deeply in the system... for example, > even #hash and #= and will be taken from the wrappee (the > compiledMethod), but not #==, as it's in ProtoObject. And #class > will never get forwarded (as it's a bytecode). > > > So maybe the #hash is the problem: on the image side, #hash gets > forwarded to the wrappee, but what does the VM do? There could > be a mismatch. (and recompiling the whole image, what bytesurgeon > installer does, could change something wrt. to hashing that > this makes it a problem whereas it might not been a problem before) I think you're right. Having a CompiledMethod as wrapper instead of a class with the doesNotUnderstand trick makes it work. Your explanation perfectly fits that for me :) Thank you, Antoine

Nov. 25, 2008

[Pharo-project] [update] #10168-10172

by Marcus Denker

-> Load FreeType Plus. (no fonts defined yet, thus it looks like before). -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 25, 2008

[Pharo-project] [update] #10167

by Marcus Denker

- clean more Preferences (Marcus Denker) - Scriptloader Seaside loading methods (Torsten Bergmann) - Postscript: (Preferences preferenceAt: #allowEtoyUserCustomEvents) changeInformee: nil changeSelector: nil. Preferences removePreference: #batchPenTrails. Preferences removePreference: #allowEtoyUserCustomEvents. Preferences removePreference: #automaticViewerPlacement. Preferences removePreference: #capitalizedReferences. Preferences removePreference: #fenceEnabled. Preferences removePreference: #keepTickingWhilePainting. Preferences removePreference: #tileTranslucentDrag. Preferences removePreference: #translationWithBabel. Preferences removePreference: #useButtonProprtiesToFire. Preferences removePreference: #alphabeticalProjectMenu. Preferences removePreference: #showAdvancedNavigatorButtons. Preferences removePreference: #ignoreStyleIfOnlyBold. Preferences removePreference: #propertySheetFromHalo. -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 25, 2008

Re: [Pharo-project] Wrapper bug (is ByteSurgeon the cause of it ?)

by Marcus Denker

On 14.11.2008, at 16:59, Antoine Marot wrote: > Hi all, > > I have a very strange bug when I use method wrappers. > > Here is my wrapper code (actually it does nothing but calling the > method) : > > ProtoObject variableSubclass: #Wrapper > instanceVariableNames: 'compiledMethod' > classVariableNames: '' > poolDictionaries: '' > category: 'Wrapper-Core' > > Wrapper>>#doesNotUnderstand: aMessage > ^aMessage sendTo: compiledMethod > > Wrapper>>#run: aSymbol with: arguments in: rec > ^rec > withArgs: arguments > executeMethod: compiledMethod > > Wrapper>>#compiledMethod: c > compiledMethod:=c. > ^self > > > Now I want to execute this : > > SequenceableCollection methodDict at: #copyFrom:to: put: (Wrapper > new compiledMethod: (SequenceableCollection>>#copyFrom:to:)). > Very strage... I think in general it is not good to use the doesNotUnderstand trick so deeply in the system... for example, even #hash and #= and will be taken from the wrappee (the compiledMethod), but not #==, as it's in ProtoObject. And #class will never get forwarded (as it's a bytecode). So maybe the #hash is the problem: on the image side, #hash gets forwarded to the wrappee, but what does the VM do? There could be a mismatch. (and recompiling the whole image, what bytesurgeon installer does, could change something wrt. to hashing that this makes it a problem whereas it might not been a problem before) Another thing: you need to empty the VM cashes when installing a method by calling #flushCache (or use Bahvior>>#basicAddSelector:withMethod:). Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Nov. 25, 2008

Re: [Pharo-project] Pharo-dev logo :)

by Damien Cassou

On Tue, Nov 25, 2008 at 1:21 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> Really cool :-). I like it but I can't include it because in a few >> weeks there won't be pharo-dev releases anymore. >> > why so? Because Pharo will include dev tools. My work will go from a distinct distribution to the official release. -- Damien Cassou http://damiencassou.seasidehosting.st

Nov. 25, 2008

Re: [Pharo-project] Pharo-dev logo :)

by Igor Stasenko

2008/11/25 Damien Cassou <damien.cassou(a)gmail.com>: > On Tue, Nov 25, 2008 at 9:36 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> Hope it not hurts anyone's feelings.. >> Just for fun :) > > Really cool :-). I like it but I can't include it because in a few > weeks there won't be pharo-dev releases anymore. > why so? > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Nov. 25, 2008