- Pharo-dev - lists.pharo.org

[Pharo-project] Mac VM 5.2.b2 ships
by John M McIntosh Jan. 4, 2010

Jan. 4, 2010

I've push the latest cocoa based 32/64bit macintel/powerpc VM There was a back-leveled patch for the JPEG2 read/writer which causes the Seasides tests to crash the VM. This is fixed. Look for the folder experimental/64bits in the regular places found via http://smalltalkconsulting.com/squeak.html or ftp://ftp.smalltalkconsulting.com/experimental/64bit/32bitImage*64bitVM/ file name: Squeak 64-32 5.2b2.app.zip This *beta* VM runs in 32 or 64 bit mode on macIntel, and 32bit mode on powerpc to support Squeak 32bit images. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

3 3

[Pharo-project] [update 1.1] #11136
by StÃ©phane Ducasse Jan. 4, 2010

Jan. 4, 2010

> 11136 > ----- > > - Issue 1738: CompiledMethodTrailer post action > > So now this should be fixed. > I should remove createHeader: > I will do that during the next batches tomorrow evening. > > Stef > > >

1 0

[Pharo-project] [update 1.1] #11135
by StÃ©phane Ducasse Jan. 4, 2010

Jan. 4, 2010

11135 ----- fixing trailer: #(0 0 0 0) by adding first createMethod: numberOfBytesForAllButTrailer header: headerWord

1 0

[Pharo-project] [update 1.1] #11126 - 27 (final methodTrailer cool cleanup
by StÃ©phane Ducasse Jan. 4, 2010

Jan. 4, 2010

BIG THANKS igor!!! 11127 ----- - Issue 1690: New Method Trailer part 7 (cs 9)

5 17

Re: [Pharo-project] What about killing PharoWeb images?
by Dale Henrichs Jan. 4, 2010

Jan. 4, 2010

----- csrabak(a)bol.com.br wrote: | > 3) Tomorrow we can have AidaWeb images based in | > pharo (please Janko!!) so we can just do the same and put the link | > to those images. | | While I'm fond of the idea on having AidaWeb very soon as possible, I | also think we should put ourselves in Janko's shoes and understand | that he'll need to master Metacelllo to arrive at the packaging. . . Being able to easily load AidaWeb into GemStone was one of the other motivations for Metacello:) My todo list for Pharo, includes building a configuration for AidaWeb that will load AidaWeb into GLASS or Pharo (with feedback from Janko). I also plan incorporate Julian's work on Pier2 for Seaside3.0 into the Pier configuration (the current Pier configuration in MetacelloRepository is for Seaside2.8 only) Dale

2 1

[Pharo-project] About moving tmp closer their use
by StÃ©phane Ducasse Jan. 4, 2010

Jan. 4, 2010

Hi guys in squeak a week ago nicolas pushed a cool (from my taste) changes that refactored the complete system so that |temp| declaration would be at the scope where they are used. This is not clear that this is an optimisation but I like the fact that temp are defined at the right place. Now it may lead to code that is a bit less readable in the sense that your temps are not systematically listed at the beginning of the method but occasionally in the closures that use them. >From my hackish lisping state of mind I like it now what do you prefer? Stef

5 5

Re: [Pharo-project] [squeak-dev] Re: 64 bit images (was Re: The Trunk: Collections-dtl.268.mcz)
by Laval Jannik Jan. 4, 2010

Jan. 4, 2010

Hi Andreas, > This may be the stupid question of the day, but can someone explain to me why we aren't just hard-wiring the word size (say in a CompiledMethod class var or so)? It's not like the primitive would *ever* return anything else unless you grind the image through SystemTracer, the value of wordSize is initialized only one time, If wordSize is nil, it takes the value of the primitive 40. > and if you do that, SystemTracer can simply update those values. Yes, it does. SystemTracer pushes the value of primitive 40 in wordSize. > It seems silly to build caches, primitives, cache invalidation for a value which will never ever change dynamically. Besides I think the cache invalidation might be wrong - The "cache" is synchronized with the VM only one time after the creation of the image, I think it is better than a hard-writing value. > how do you know that initialPC or other word size related methods aren't sent before the startUp method is executed? startUp method is the first method executed at the startup, no ? But in SystemTracer, the value is initialized in "clonePreStartup" method. So there is no problem with potential method calls before startUp. > > Cheers, > - Andreas Cheers, --- Jannik Laval ---

1 0

[Pharo-project] Can't use <Enter> key to select notifier action
by danklein Jan. 4, 2010

Jan. 4, 2010

When a notifier pops up, you can tab (or shift-tab) to the Proceed/Abandon/Debug/Create buttons at the top of the window. However, when the one you want is highlighted, I would like to be able to just press the to execute it, but you have to actually click on it. Is there a configuration setting to affect this behavior? -- View this message in context: http://n2.nabble.com/Can-t-use-Enter-key-to-select-notifier-action-tp419464… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

5 4

[Pharo-project] Does someone know why Nile is in Dev images?
by Mariano Martinez Peck Jan. 4, 2010

Jan. 4, 2010

Does another package of the dev image depends on Nile? If not, I don't understand why it is part of the dev image. I see it as any other external package but not a "dev tool" that should be included. Thanks Mariano

4 6

Re: [Pharo-project] 64 bit images (was Re: [squeak-dev] The Trunk: Collections-dtl.268.mcz)
by Laval Jannik Jan. 4, 2010

Jan. 4, 2010

Hi, I made a new version of the system-tracer (in attachment). It works fine with the latest pharo version. For wordSize, we decide to create a instance variable in SmalltalkImage, which is initialized at startup. The method initialPC is: --- initialPC "Answer the program counter for the receiver's first bytecode." ^ (self numLiterals + 1) * SmalltalkImage current wordSize + 1 --- The fix will be integrated in Pharo soon. It is also in attachment. Cheers On Jan 3, 2010, at 06:46 , John M McIntosh wrote: > Ok, well I was hoping that Laval Jannik would review the changes/solution in http://bugs.squeak.org/view.php?id=7430 > then update his original System-Tracing.2forPharo3.cs Then test to confirm we can build a 64bit image from the current Pharo image > > > On 2010-01-02, at 6:46 PM, David T. Lewis wrote: > >> John, one additional note. >> >> The SystemTracer changesets currently in circulation have an obsolete >> implementation of SystemDictionary>>wordSize.The original 64-bit >> Squeak used vmParameterAt: 27 for the VM to answer its word size, >> but this was later changed to vmParameter at: 40. This is the reason >> that the original "dist3" 64-bit image does not work on current VMs. >> >> You will want to revert #wordSize back to a current version >> so that it uses vmParameter at: 40. >> >> This issue will go away when we implement the cached #wordSize fixes >> discussed separately (http://bugs.squeak.org/view.php?id=7430) but >> I wanted to mention it because I spotted the obsolete method in the >> System-Tracing2forPharo.cs change set. >> > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > --- Jannik Laval ---

2 3