February 2015 - Pharo-dev - lists.pharo.org

[Reflectivity] Trello Board
by Marcus Denker Feb. 28, 2015

Feb. 28, 2015

Hi, I added a board for this one, too https://trello.com/b/m5cxaAxB/reflectivity <https://trello.com/b/m5cxaAxB/reflectivity> Marcus

1 0

[Pharo4][Slots] Trello Board
by Marcus Denker Feb. 28, 2015

Feb. 28, 2015

Hi, I want to try to keep the TODO in a Trello board, this should make it easier for people that want to help to pick something todoâ¦ I will post some simple actions, too. (for example tests that need to be written). https://trello.com/b/d59lgZFB/slots <https://trello.com/b/d59lgZFB/slots> Marcus

1 0

Zn using String>>#substrings:
by Sven Van Caekenberghe Feb. 28, 2015

Feb. 28, 2015

Hi, Zinc HTTP Components' latest stable version 2.6.2 which was integrated in Pharo 4.0 is using String>>#substrings: instead of String>>#subStrings: For Pharo 4 this is of course OK. String>>#substrings: was also added to Pharo 3.0. For Pharo 2.0 Zinc will load a 'forward compatibility' package to add the missing method. If you are working in/with an older/existing Pharo 3.0 things will not be solved automatically. Either add the method yourself, or load 'Zinc-pharo2-forward-compatibility' manually. It might even be possible to update the image, but I haven't tried that. HTH, Sven

1 0

Unkownselector Warning: removed for now
by Marcus Denker Feb. 28, 2015

Feb. 28, 2015

Hi, With the AST changes, we now create the RBMessageNode with a selector. Before it was an array of parts, which means that the Symbol was not created in the Parser. This means, we used to check in the Semantic Analysis when visiting the RBMessageNode if the selector already is in the Symboltable and raise a warning else. After discussing with Pablo, we decided to not implement this functionality on the level of the Parser (where the symbol is now created). - this is purely a âlintâ like warning. It has nothing to do with Syntax (nor with semantics). - it should be implemented on the tool level - it should not raise the annoying dialog, but instead put a red line under the symbol - The non existing selector is coloured red by the syntax highlighting already now (until you acceptâ¦) Thus: We will for now remove the warning, it will come back as part of the IDE later. There we will be able to do a *much* better job, too. (e.g. not check against existing symbols, but existing method selectors). Marcus

1 1

The evil twin in 40516
by Marcus Denker Feb. 28, 2015

Feb. 28, 2015

Hi, In 40516 there is now a strange, but rather powerful mechanism for CompiledMethod: the Twin. What does that do? you can call on a method #createTwin (ReflectivityExamples>>#exampleMethod) createTwin. after this, the CompiledMethod has a high-level representation (the AST) attached that itself references the CompiledMethod (they form a twin). (ReflectivityExamples>>#exampleMethod) reflectiveMethod The fun thing is now that one can install either in the class. Call #invalidate to make sure the reflective method is installed. ReflectiveMethod implements #run:with:in: which calls a compilation hook (too re-create from the AST) and then installs that in the method dict and then executes the method: (ReflectivityExamples>>#exampleMethod) createTwin. (ReflectivityExamples>>#exampleMethod) invalidate. self assert: (ReflectivityExamples>>#exampleMethod) class = ReflectiveMethod. self assert: ReflectivityExamples new exampleMethod = 5. self assert: (ReflectivityExamples>>#exampleMethod) class = CompiledMethod. Which means that this gives us an in-image, on-demand JIT compiler AST->Bytecode. In 50 lines of code. e.g. try on Morph: Morph methods do: #createTwin. Morph methods do: #invalidate. Counting which twin is installed shows us the working set of Morph: (Morph methods select: [ :each | each class = CompiledMethod ]) size some 330 method out of nearly 900â¦. So what can one do with this? In essence this turns the AST into a reflective representation for Methods (if you care to set up twin creation + invalidation correctly). What will this allow us to do? stay tuned... Marcus

9 29

About slots and syntax
by stepharo Feb. 28, 2015

Feb. 28, 2015

Hi guys I was reading the definitions we sent around and I have some questions about => Object subclass: #TestLocal slots: { #local => ProcessLocalSlot } classVariables: { } category: 'SlotTestGuille'. Object subclass: #TestLocal2 slots: { #local => ProcessLocalSlot default: 5} classVariables: { } category: 'SlotTestGuille'. Are we sure that we want to use that => I thought about = but this is not an assignement this is a declaration and normally we use | for declaration. So what would be other alternatives before the world use => Then I still do not understand why we have empty classVariables: to me it does not make sense. I do not get why we like to have empty collections for the sake of having empty collections. We are trapped in some strange ways of thinking. Object subclass: #TestLocal slots: { #local => ProcessLocalSlot } classVariables: { } category: 'SlotTestGuille'. => Object subclass: #TestLocal slots: { #local => ProcessLocalSlot } package: 'SlotTestGuille'.

3 2

Postdoc position at INRIA Chile
by Alexandre Bergel Feb. 28, 2015

Feb. 28, 2015

Dear All, I have just received a announcement for a position at INRIA Chile. Here is an extract from the call. It is written in Spanish, however it is also open to non-spanish speaker. "Inria Chile fue creado en Chile en 2012 por Inria (www.inria.fr) y en colaboracioÌn con 9 universidades chilenas. Cuenta con el apoyo de CORFO, que seleccionoÌ el proyecto de Inria Chile en el marco del concurso AtraccioÌn de Centros de Excelencia Internacional para la Competitividad dedicado a desarrollar y reforzar las capacidades I+D del paiÌs. Inria Chile desarrolla sus actividades I+D a traveÌs de una plataforma de desarrollo de acciones aplicadas, que busca proponer soluciones a desafiÌos econoÌmicos y sociales para Chile, tal como energiÌa, en particular energiÌas renovables, recursos naturales y âciudades inteligentesâ. TambieÌn se estaÌ trabajando en temas aplicados como desarrollo sustentable, gestioÌn de cataÌstrofes naturales o el desarrollo de tecnologiÌas avanzadas para la astronomiÌa. Buscamos a un postdoc interesado en trabajar part-time en estrecho viÌnculo con un equipo de desarrollo que lleva a cabo una de estas acciones. Las competencias requeridas son particularmente en las aÌreas de: aprendizaje, datos masivos, redes de sensores, visualizacioÌn interactiva. Esta lista no es exhaustiva.â If you have a PhD and are interested, please contact me! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 1

[pharo-project/pharo-core]
by GitHub Feb. 27, 2015

Feb. 27, 2015

Branch: refs/tags/40521 Home: https://github.com/pharo-project/pharo-core

1 0

zipped and unzipped methods for ByteArray
by Juraj Kubelka Feb. 27, 2015

Feb. 27, 2015

Can I add ByteArray>>#zipped and #unzipped methods the way it is for String? I want to compress bytes before sending through internet, for example. Do you agree? Thanks, Juraj

5 6

Recording user actions in GTools
by Andrei Chis Feb. 27, 2015

Feb. 27, 2015

Hi, In order to better understand how people use the GT tools we would like to integrate, before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data. The recording of data will be opt-out: *you have to explicitly agree with sending usage data*. The first time you open a GT tool, that tool will embed a small UI asking you if you want to enable data submission. We will save the setting in the your preference directory so it will be shared between all your local images. You can change this setting at any time from the Settings Browser. For now we will only like to collect data about Spotter. *By default we will only collect anonymous data *about various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc) without collecting any data what about what query you enter or what search results you get. We would also add an optional setting for sending the query text and selected elements. We will send then the data periodically to our server and when you close the image. The data that will be send is rather small: 1000 actions require 7kb of data. Thus sending an entire day worth of recordings, if all you did that day was searching, should be around 1MB of data. The recording does not influence the performance of Spotter. Spotter already generates all events of interest as announcements. To enable recording we just register a subscriber with the Spotter announcer and store the events of interest. We would like to get your opinion on this. Cheers, GT team

8 10