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

[Pharo-project] How to query the owner package of a RPackage ?
by Alain Plantec April 5, 2012

April 5, 2012

Hi all, Since a RPackage can have sub-packages (see RPackage>>systemSubPackages) I'm wondering how to get the parent package of a package. btw: why are subPackages computed ? I mean it seems to me that a package can be considered as a composite, so why not directly associate a package with its children ? (and maybe have a two ways association between a child and a parent package). ----- RPackage>>systemSubPackages "return all RPackages matching with systemCategories of this RPackage" |tmpPackages| tmpPackages := OrderedCollection new. self systemCategories do: [:aString | (aString asSymbol = self name) ifFalse: [ |tmpPackage| "Maybe a RPackage matching the subcategory name does not yet exist in the organizer (Because packageInfo lazily register category from system). In this case, We should also lazily register a new RPackage with the right contents inside:" tmpPackage := RPackageOrganizer default packageNamed: aString asSymbol ifAbsent: [RPackageOrganizer default importFromPackageInfo: (PackageInfo named: aString)]. tmpPackages add: (tmpPackage). ]. ]. ^ tmpPackages ----- Thanks Alain

3 2

[Pharo-project] [ANN] new stable version of omnibrowser
by Guillermo Polito April 5, 2012

April 5, 2012

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

4 4

[Pharo-project] Limit of the #become:
by Mariano Martinez Peck April 5, 2012

April 5, 2012

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

5 6

[Pharo-project] Pharo 1.4 with interpreted VM
by Hilaire Fernandes April 5, 2012

April 5, 2012

Is there any way to get a 1.4 Pharo image saved with the interpreted VM binary format? I need that to produce a XO application, the stack VM is missing some part to work with Sugar launch system Hilaire -- Dr. Geo -- http://www.drgeo.eu

6 6

[Pharo-project] type-inference: it works!
by Francisco Garau April 4, 2012

April 4, 2012

Load the attached ChangeSets: first Ti-Engine and then Ti-Support. You could then evaluate the below expressions -- watch the Transcript to see which methods are being analysed. TiSystem current reset. string := '3 + 4'. Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. "=> return {<SmallInteger>} " TiSystem current reset. string := 'Display boundingBox'. Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. "=> return {<Rectangle origin: <Point x: <SmallInteger> y: <SmallInteger>> corner: <Point x: <SmallInteger> y: <SmallInteger>>>}" TiSystem current explore. Analysing 'Display boundingBox' shows a couple of surprises: 1. The code never goes through the #new method (it creates objects using #basicNew and #@) 2. Object code goes through Object>>value but knowing that the implementation just answers self, it could be easily optimised. I will try to package it more nicely under Monticello -- there are still a few rough edges that need to be polished before getting it to the same state it was in 2001... Cheers, Francisco

5 21

[Pharo-project] CFP: 6th Workshop on Dynamic Languages and Applications (DYLA'12)
by Damien Cassou April 4, 2012

April 4, 2012

=================================================================== 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

1 0

[Pharo-project] [update 1.3] #13328
by Marcus Denker April 4, 2012

April 4, 2012

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

1 0

Re: [Pharo-project] [update 1.4] #14421
by Marcus Denker April 4, 2012

April 4, 2012

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

1 0

Re: [Pharo-project] [update 1.4] #14421
by Marcus Denker April 4, 2012

April 4, 2012

On Apr 4, 2012, at 5:05 PM, Damien Cassou wrote: > On Wed, Apr 4, 2012 at 4:47 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> (first one :) > > and good one. Thank you > The reason why we decided to rename FS is that it will be used very deeply in the system. e.g. reading startup scripts.... so it is not an external package and loading an new version of FS on top could have very bad effects. 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. Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] [Pharo 1.4] Please test!
by Marcus Denker April 4, 2012

April 4, 2012

You can download the lastest 1.4 here for testing: https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSucces… And a first version of the one-click here: https://ci.lille.inria.fr/pharo/job/Pharo%20One%20Click%20image/lastSuccess… -- Marcus Denker -- http://marcusdenker.de

12 20