- Pharo-dev - lists.pharo.org

[Pharo-project] TORCH: supporting source-code change integration
by Veronica Isabel Uquillas Gomez May 28, 2010

May 28, 2010

Dear all, I would like to announce Torch, a tool for supporting source-code change integration. For now, it offers visualizations of the changes and enhanced change lists. Torch can be accessed through Monticello (in the main MC browser, in the repository browser or in the history browser). Selecting a version or slice, you can view the changes with Torch using the contextual menu. Once you open the Torch dashboard, you can access the enhanced change list or a detailed visualization via the contextual menu as well. Torch is available on SqueakSource, the repository is named Torch, and you need to load the ConfigurationOfTorch package. It runs in a dev or core image. For a dev image. - ConfigurationOfTorch loadVersion10 For a core image. 1) Set fonts - described in the attached file. 2) ConfigurationOfTorch loadDefault I would appreciate comments and feedback! Best Regards, VerÃ³nica Uquillas GÃ³mez Vrije University Brussel - SOFT Lab University of Lille - RMOD Team

5 18

[Pharo-project] Fwd: [Vm-dev] Squeak removed from Gentoo Linux
by StÃ©phane Ducasse May 28, 2010

May 28, 2010

Reading the complete thread is quite interesting. Stef Begin forwarded message: > From: Bert Freudenberg <bert(a)freudenbergs.de> > Date: May 27, 2010 7:37:54 PM GMT+02:00 > To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > Subject: [Vm-dev] Squeak removed from Gentoo Linux > Reply-To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > > Squeak was recently removed from Gentoo Linux Ebuilds because of security issues in our bundled plugins: > > http://bugs.gentoo.org/show_bug.cgi?id=247363 > > While it is convenient for us to bundle external library sources, package maintainers do not like that practice. Is there anything we can realistically do about it? > > - Bert - >

2 2

[Pharo-project] [update 1.1] #11377
by StÃ©phane Ducasse May 28, 2010

May 28, 2010

11377 ----- - Issue 2460: NewTextMorphTests #testClassDefinitionMorphCreation and #testMethodMorphCreation fails Rethought the CodeMorph class hierarchy, removed the subclasses and added CodeMorph class methods for creating MethodMorph and ClassDefinitionMorph. Thanks Fernando. - Issue 2182: Testing if a class is obsolete. Part One. Thanks alex. - Issue2458: ChooseColorDefaults. Thanks Henrik. - Issue 1832: remove unnecessary halt or convert them into error. Thanks Guille Stef

1 0

[Pharo-project] A port of Pharo: Redline Smalltalk ...
by James Ladd May 28, 2010

May 28, 2010

Hi Pharo-ites, I'm working on a port of Pharo to the Java Virtual Machine called Redline Smalltalk. (read more here: http://jamesladdcode.com/?p=323) I'm wanting to port every single class over time, but initially enough to get the compiler working and have a minimum runtime. Of the 1600+/- classes which are those necessary to make a small workable compiler and runtime environment? Rgs, James. _________________________________________________________________ Need a new place to live? Find it on Domain.com.au http://clk.atdmt.com/NMN/go/157631292/direct/01/

3 2

Re: [Pharo-project] [squeak-dev] Re: New weak finalization support. Implementation
by Igor Stasenko May 28, 2010

May 28, 2010

Guys, it looks like i found an elegant solution. Please check the new-finalization-auto.2.cs, which i uploaded to http://bugs.squeak.org/view.php?id=7473. It adds just a few things: initTestPair TestItem := WeakFinalizerItem new list: TestList object: Object new. checkTestPair HasNewFinalization := TestList swapWithNil notNil. These two method is then sent from within WeakArray's finalization process: finalizationProcess [true] whileTrue: [ WeakFinalizationRegistry initTestPair. FinalizationSemaphore wait. FinalizationLock critical: [ WeakFinalizationRegistry checkTestPair. FinalizationDependents do: [:weakDependent | weakDependent ifNotNil: [weakDependent finalizeValues]]] ifError: [:msg :rcvr | rcvr error: msg]. ]. And so, at each GC cycle, a new registry it knows exactly if it allowed to do a shortcut, or not. And if not, then it behaves in same way as old registry - it starts scanning the whole dictionary to clean graveyard. So, in summary: running on older VMs , a WeakFinalizationRegistry will behave exactly as old WeakRegistry. While on VMs, which supporting new finalization, it will do a shortcut. This is at cost of extra 2 objects, allocated per GC cycle, to detect if new finalization is supported. P.S. oops, actually it could be just one object.. just need to change two methods at WeakFinalizationRegistry class side: initialize TestList := WeakFinalizationList new. TestItem := WeakFinalizerItem new. initTestPair TestList swapWithNil. "make sure list is empty" TestItem list: TestList object: Object new. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Struct with doubles
by Schwab,Wilhelm K May 27, 2010

May 27, 2010

Hello all, I am faced with some win32 software that uses a structure like struct gizmo { double x; y; z; double q[4]; } Would it be legal to treat that as struct gizmo { double x; y; z; double q0; q1; q2; q3; } and then let Pharo define the fields? This is running on 32 bit winxp. A colleague is doing 3D magic with the resulting numbers, but Weird things appear to be happening. I am looking for ways that I might be causing them. It is also possible that the gizmo to which we are interfacing is just plain broken. Bill

1 0

[Pharo-project] [update 1.1] #11376
by StÃ©phane Ducasse May 27, 2010

May 27, 2010

11376 ----- - Issue 2440: Collection - Math functions protocol. Thanks Henrik I cleaned also some code.

1 0

May 27, 2010

Does anybody know what defineApplicationView and defineFactoryView are doing? ;) Stef

1 0

May 27, 2010

11375 ----- - Issue 767: BlockClosure decompile bug. Thanks nicolas and henrik. - Rewrite = nil to isNil. Thanks Gabriel Stef

1 0

[Pharo-project] Integrating VMMaker-dtl.175
by Igor Stasenko May 27, 2010

May 27, 2010

Dear all, i would really like to finish an integration of new finalization. But this requires releasing a new VMs for all platforms. If you think, we're done with VM-side part, then lets proceed with releasing new VMs, so we could start using new feature. -- Best regards, Igor Stasenko AKA sig.

2 3