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

Re: [Pharo-project] Pharo 1.4 - browse slow??

by Camillo Bruni

which vm? which browser? On 2012-04-04, at 18:32, Schwab,Wilhelm K wrote: > I'm seeing ~1-2 second delays on any attempt to browse a class. Anyone else?

April 4, 2012

[Pharo-project] CFP: 6th Workshop on Dynamic Languages and Applications (DYLA'12)

by Damien Cassou

=================================================================== 6th Workshop on Dynamic Languages and Applications Colocated with 26th European Conference on Object-Oriented Programming (ECOOP 2012) 11â16 June 2012, Beijing, China =================================================================== Web site: http://scg.unibe.ch/wiki/events/dyla2012 The DYLA Workshop series focuses on the revival of dynamic languages. These days, dynamic languages (like Lisp, Ruby, Python, JavaScript, Lua, etc...) are getting ever more popular. This is a call to arms for academia! We need to explore the future of dynamic languages through its human aspects and technical issues. We also ought to look back and pick up solutions from existing dynamic languages (such as Scheme, Smalltalk, or Self) to be rediscovered and spread around. Goal and Topics The goal of this workshop is to act as a forum where we can discuss new advances in the design, implementation and application of dynamically typed languages that, sometimes radically, diverge from the statically typed class-based mainstream with limited reflective capabilities. Another objective of the workshop is to discuss new as well as older âforgottenâ languages and features in this context. The workshop will have a demo-oriented style. The idea is to allow participants to demonstrate new and interesting features and discuss what they feel is relevant for the dynamic language community. All participants need to submit a two-page description (LNCS format) of their presentation or/and tool demonstration. Each accepted paper will be presented for 20â30 minutes. Moreover, all workshop attendees will be asked to give 10-minute âlightning demosâ of whatever they bring with them. A dedicated session will be allocated for this, provided there is ample time available. A session on pair programming is also planned. People will then get a chance to share their technology by closely interacting with other participants. Submission page is http://www.easychair.org/conferences/?conf=dyla2012 The expected audience of this workshop is practitioners and researchers sharing the same interest in dynamically typed languages. Lua, Python, Ruby, Scheme and Smalltalk are gaining a significant popularity both in industry and academia. However, each community has the tendency to only look at what it produced. Broadening the scope of each community is the goal of the workshop. To achieve this goal we will form a PC with leading persons from all languages mentioned above, fostering participation from all targeted communities. Topics of interest include, but are certainly not limited to: - what features make a language a dynamic one? - agents, actors, active object, distribution, concurrency and mobility - delegation, prototypes, mixins, traits - first-class closures, continuations, environments - reflection and meta-programming - (dynamic) aspects for dynamic languages - higher-order objects & messages - other exotic dynamic features - multi-paradigm & static/dynamic-marriages - (concurrent/distributed/mobile/aspect) virtual machines - optimization of dynamic languages - automated reasoning about programs written in dynamic languages - improved or novel IDE support for dynamic languages - empirical studies about the application of dynamic languages - best practices and patterns specific to dynamic languages - use of dynamic features by library & framework developers - reverse engineering and analysis of dynamic applications - program correctness through unit testing (as opposed to types) - applications of dynamic languages: embedded systems, robotic systems, web site, ... And any topic relevant in applying and/or supporting dynamic languages: Smalltalk, Python, Ruby, Javascript, Scheme, Lisp, Self, ABCL, Prolog, Ioke, Clojure and many more... Important dates - Due date for full workshop papers submission: April 17th, 2012 - Notification of acceptance: April 27th, 2012 - Workshop: June 12th, 2012 Organizers - Alexandre Bergel, University of Chile, Santiago, Chile - Damien Cassou, Arles research group at INRIA, France - Jorge Ressia, University of Bern, Switzerland - Serge Stinckwich, UMMISCO, IRD/UPMC/VNU, Vietnam Program Committee - Alexandre Bergel, University of Chile, Santiago, Chile - Carl Friedrich Bolz, Heinrich-Heine-UniversitÃ¤t, Germany - Camillo Bruni, Camillo Bruni, RMoD, INRIA, France - Damien Cassou, Arles research group at INRIA, France - Adrian Kuhn, UBC, Canada - Olivier Michel, UPEC, France - Lukas Renggli, Google, Switzerland - Jorge Ressia, University of Bern, Switzerland - Serge Stinckwich, UMMISCO, IRD/UPMC/VNU, Vietnam - Juan Pablo Sandoval Alcocer, University of Chile, Chile

April 4, 2012

[Pharo-project] Pharo 1.4 - browse slow??

by Schwab,Wilhelm K

I'm seeing ~1-2 second delays on any attempt to browse a class. Anyone else?

April 4, 2012

Re: [Pharo-project] Limit of the #become:

by Mariano Martinez Peck

On Wed, Apr 4, 2012 at 5:32 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Hi guys. I noticed that there is a limit in the number of objects you can > become. In my case, I am becoming 2312157 objects. So..I don't expect that > the become works. I imagine that it was not designed for so many objects in > mind ;) > However, what I would really understand is where is the limitation and the > reason. And of course, if someone already knows which is the real number > limit. Otherwise, I will do a kind of binary search and discover it. > > If you want to reproduce it: > > | dict | > dict := Dictionary new. > 2312157 timesRepeat: [ dict at: Object new put: Object new ]. > 3 timesRepeat: [Smalltalk garbageCollect]. > dict keys elementsForwardIdentityTo: dict values. > > throws a #primitiveFailed. > Of course the following works correctly: | dict tmp | dict := Dictionary new. 2312157 timesRepeat: [dict at: Object new put: Object new]. 3 timesRepeat: [Smalltalk garbageCollect]. dict associations groupsOf: 50000 atATimeDo: [:each | tmp := Dictionary withAll: each. tmp keys elementsForwardIdentityTo: tmp values ] So... indeed, there seems to be a limit with the amount of objects. > > Thanks, > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

April 4, 2012

[Pharo-project] [update 1.3] #13328

by Marcus Denker

13328 ----- Issue 5579: Another Zn Update http://code.google.com/p/pharo/issues/detail?id=5579 -- Marcus Denker -- http://marcusdenker.de

April 4, 2012

Re: [Pharo-project] [ANN] new stable version of omnibrowser

by StÃ©phane Ducasse

fabrizio did you try nautilus ? Stef On Apr 4, 2012, at 2:24 PM, Fabrizio Perin wrote: > Thanks really a lot for this, > I was trying to find sometime to do it myself. I'm finishing to setup a local Jenkins build to load Moose together with OB. Manually it work. I will report any unusual behaviour. > > Cheers, > Fabrizio > > 2012/4/2 Guillermo Polito <guillermopolito(a)gmail.com> > I fixed some usages of deprecated code, and now it loads and works at first in the latest -hopefully and almost released- Pharo 1.4 > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOmniBrowser'; > load. > > (ConfigurationOfOmniBrowser > project version: #stable) load: #( 'Dev' 'Dev Tests'). > > This scripts installs OmniBrowser + OCompletion + Refactoring Browser > > Please test :) > > Guille >

April 4, 2012

Re: [Pharo-project] [update 1.4] #14421

by StÃ©phane Ducasse

I loved that one :) Your first integration :) Supercool. Stef On Apr 4, 2012, at 4:47 PM, Esteban Lorenzano wrote: > 14421 > ----- > > Issue 5534: Do we rename/sync FS for 1.4? > http://code.google.com/p/pharo/issues/detail?id=5534 > > (first one :) >

April 4, 2012

[Pharo-project] Limit of the #become:

by Mariano Martinez Peck

Hi guys. I noticed that there is a limit in the number of objects you can become. In my case, I am becoming 2312157 objects. So..I don't expect that the become works. I imagine that it was not designed for so many objects in mind ;) However, what I would really understand is where is the limitation and the reason. And of course, if someone already knows which is the real number limit. Otherwise, I will do a kind of binary search and discover it. If you want to reproduce it: | dict | dict := Dictionary new. 2312157 timesRepeat: [ dict at: Object new put: Object new ]. 3 timesRepeat: [Smalltalk garbageCollect]. dict keys elementsForwardIdentityTo: dict values. throws a #primitiveFailed. Thanks, -- Mariano http://marianopeck.wordpress.com

April 4, 2012

Re: [Pharo-project] [update 1.4] #14421

by Marcus Denker

On Apr 4, 2012, at 5:27 PM, Damien Cassou wrote: > On Wed, Apr 4, 2012 at 5:08 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> With renaming, people can load the official FS package easily, while we can >> be very cautious with the code that is run on image startup and save. > > it makes sense. But how are you going to apply changes made in > official FS to Pharo? > That is the question.... but people where very upset about having an "optional" package in Pharo that they wanted to load themselves.. you can not have everything. Marcus -- Marcus Denker -- http://marcusdenker.de

April 4, 2012

Re: [Pharo-project] [Pharo 1.4] Please test!

by Marcus Denker

On Apr 4, 2012, at 5:23 PM, Hilaire Fernandes wrote: > > > Also clean up is not as good as before, cleaned image is still 22MB (in > contrast to about 10MB with 1.3) > This is strange... ScriptLoader new cleanUpForProduction generates a 8.4 MB Image... What you should check is that #cleanUpForProduction changes a bit, it is much simpler now (I move more stuff to the #cleanUp: methods and we cleaned up the image in general a little): cleanUpForProduction "self new cleanUpForProduction" "trim MC ancestory information" MCVersionInfo allInstances do: [ :each | each instVarNamed: 'ancestors' put: nil ]. "delete logo" PolymorphSystemSettings showDesktopLogo: false. "unload packages" Smalltalk globals at: #SUnitUnloader ifPresent:[ :unloader | unloader new unloadAll ]. (MCPackage named: 'HelpSystem-Core') unload. (MCPackage named: 'FixUnderscores') unload. (MCPackage named: 'Deprecated14') unload. self cleanUpForRelease. (MCPackage named: self theScriptLoaderPackageName) unload. Smalltalk cleanUp: true except: #() confirming: false. Smalltalk garbageCollect. -- Marcus Denker -- http://marcusdenker.de

April 4, 2012