- Pharo-dev - lists.pharo.org

[Pharo-project] Closure review
by Michael Roberts Sept. 7, 2009

Sept. 7, 2009

can someone point me to any of the following 1) a definitive set of changesets or MC packages we applied for the closure integration 2) a definitive squeak (or other) image with closures integrated. Did Elliot publish a closure image? i ask because i'm trying to hunt down a debugger bug. I downloaded Squeak 3.10.2 but I don't think that has closures (?). I tried to update it to trunk but the process stalled. i'm not up on squeak these days - is there a snapshot of the trunk somewhere? Anyway just looking for another image i can use to compare method versions. thanks! Mike

2 2

[Pharo-project] New Pharo based on core 10440
by Damien Cassou Sept. 7, 2009

Sept. 7, 2009

I've just uploaded new Pharo and Pharo-web images based on 10440: http://pharo-project.org/pharo-download. Refactorings should work again. Please report any issue -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0

[Pharo-project] The better debugger support by extending an Object protocol
by Igor Stasenko Sept. 7, 2009

Sept. 7, 2009

Hello guys, i'd like to discuss with you an idea of having a specific methods in Object class for a better and more clever behavior when debugging. For those of you who are using different kinds of proxies, the main problem with them that you should override the #printOn: or #printString methods in order to behave them similar to what original(proxied) object should be, but from other side, especially for debugging purposes, this incurs a major inconvenience, because you often need to differentiate between the real object and object proxy while debugging. Because if proxy behaves similar to proxied object while printing, you can't really make a difference when looking at it. So, i thought that a nice solution would be to extend an Object protocol especially for debugging purposes by adding #debugPrintOn: method and change the debugger to use this message, instead of #printOn: for displaying objects in inspector panels. Here is the default implementation of Object>>debugPrintOn: aStream ^ self printOn: aStream And, as you may guess, now the proxy could choose to behave differently depending on context. P.S. Maybe i'm missing a point, and there are already the existing good practices how to get around this.. if so, then please tell me. -- Best regards, Igor Stasenko AKA sig.

5 7

[Pharo-project] Added package KernelTests-PeterHugossonMiller.145.mcz
by Peter Hugosson-Miller Sept. 7, 2009

Sept. 7, 2009

Name: KernelTests-PeterHugossonMiller.145 Author: PeterHugossonMiller Time: 4 September 2009, 2:11:41 am UUID: 1bab2752-fa51-48ab-a64d-569f6ceda5bd Ancestors: KernelTests-PeterHugossonMiller.144 Fix for Issue 1150 - Incorrect test that was meant to test Duration>>#storeOn: actually tested #printOn: instead -- Cheers, Peter

4 4

[Pharo-project] [update] 10440
by Marcus Denker Sept. 7, 2009

Sept. 7, 2009

10440 ----- Issue 897: MethodPragmaTest>>testReformat failure Issue 1164: test failure: #testClassWithInvalidClassVariablesShouldNotBeReferencedByItsSuperclass -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

1 0

[Pharo-project] Updated the list of ok committers after ESUG signature
by StÃ©phane Ducasse Sept. 7, 2009

Sept. 7, 2009

Hi I updated the list and the svn repo with the list of ok committers. Thanks for your signature! Stef

1 0

[Pharo-project] Impossible launc/use Lumiere
by nullPointer Sept. 7, 2009

Sept. 7, 2009

I try use Lumiere http://vst.ensm-douai.fr/ESUG2009Media/uploads/1/lumiereIWST-2.pdf for show a sample OpenGL window but donÂ´t works. I dont know what i doing bad.What is needed for use OpenGL in Pharo? Is a stupid idea use OpenGL under Pharo for create 2d UIs ? My idea is use Lumiere for build UIs embedded in a morphic window, but with OpenGL widgets, buttons, textboxes etc s is a possible idea? I could for example use OpenGL external widgets libs for use in Lumiere? Will be fantastic do a UIBuilder using that. If Lumiere dont works for that exists another lib o posibility? Regards -- View this message in context: http://n2.nabble.com/Impossible-launc-use-Lumiere-tp3582501p3582501.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

5 11

Re: [Pharo-project] question about Issue 207: ImageSegment discoverActiveClasses strange error
by sheridan＠sheridan-mahoney.com Sept. 7, 2009

Sept. 7, 2009

On Sep 5, 2009, at 10:46 , St?phane Ducasse wrote: > On Sep 5, 2009, at 3:10 AM, sheridan(a)sheridan-mahoney.com wrote: [...] > >> I have found a report that seems quite interesting, and have done >> some digging into the issue described here: >> http://code.google.com/p/pharo/issues/detail?id=207 >> ( ImageSegment discoverActiveClasses strange error ) >> and now I have a few questions I was hoping to get feedback on. > > > We would love to have a couple of tests for imagesegment!!!! > Adrian did you publish the ones you did? I committed my image segment tests to the inbox (Tests-AdrianLienhard. 19). There are some initial tests in ImageSegmentTest (one fails, which documents a problem of loading symbols). I also implemented support code that allows one to analyze a segment binary (i.e., to iterate over the instances in the segment without instantiating the objects). This should simplify writing more tests. Cheers, Adrian [...] ___________________ http://www.adrian-lienhard.ch/ Great! Thanks! I'll start exploring adding more tests for this area. Sheridan

1 0

[Pharo-project] Building a VM and/or plugins
by Ken.Dickey Sept. 6, 2009

Sept. 6, 2009

> "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> ... > The question then becomes whether to connect to OpenSSL via FFI/Alien or to > make a plugin. Â One absolute requirement is that the image not turn to > stone when an address is wrong, a peer crashes, or a router gets unplugged > w/o warning. Â The most obvious solution to me (please speak up if you > disagree) is to connect/bind, read/write and disconnect on a > connection-specific OS thread. I would think a separate thread (or process) is required to handle and recover from bad pointer references. For general client/server multiplexing however, you might look at liboop for ideas: http://liboop.ofb.net/ "Liboop is a low-level event loop management library for POSIX-based operating systems. It supports the development of modular, multiplexed applications which may respond to events from several sources. It replaces the "select() loop" and allows the registration of event handlers for file and network I/O, timers and signals. Since processes use these mechanisms for almost all external communication, liboop can be used as the basis for almost any application." There are refs to other event dispatchers on the liboop web page. FYI, -KenD

2 1

[Pharo-project] [ann] PharoCore-1.0-10439-BETA
by Marcus Denker Sept. 6, 2009

Sept. 6, 2009

http://gforge.inria.fr/frs/download.php/23084/PharoCore-1.0-10439-BETA.zip -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

1 0