- Esug-list - lists.esug.org

Camp Smalltalk

by Johan Brichau

To those coming to Camp Smalltalk this weekend: There is a flea market in the entire neighbourhood. This means there is also a vendor in front of our door, but I have put a sign on the door and the vendor made a passageway. Just ring the bell and I will come down to open the door. But in case you get lost: +32 476 78 64 45 Johan

Aug. 25, 2012

Re: [Esug-list] Dinner in Ghent on Friday

by HwaJongOh

See you at the Camp! 2012. 8. 23., 아침 9:22, David Chisnall 작성: > Hi, > > Is anyone around on Friday for dinner? A couple of us are planning on leaving the Ibis Gent Opera at 7:30pm in search of food. > > David > > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

Aug. 25, 2012

Re: [Esug-list] Dinner in Ghent on Friday

by Dale Henrichs

I'm in town, but meeting an old friend for drinks and dinner then early bedtime for this jet-lagged boyo:) Dale ----- Original Message ----- | From: "Sean P. DeNigris" <sean(a)clipperadams.com> | To: esug-list(a)lists.esug.org | Sent: Thursday, August 23, 2012 2:14:42 PM | Subject: Re: [Esug-list] Dinner in Ghent on Friday | | I'm getting in Friday morning... should work... | | | | -- | View this message in context: | http://forum.world.st/Dinner-in-Ghent-on-Friday-tp4645064p4645115.html | Sent from the ESUG mailing list archive at Nabble.com. | | _______________________________________________ | Esug-list mailing list | Esug-list(a)lists.esug.org | http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org |

Aug. 24, 2012

Thanks Cincom for promoting conference!

by Igor Stasenko

Seen mails in my inbox from Cincom, inviting me to ESUG conference. Just wanna say thanks. :) -- Best regards, Igor Stasenko.

Aug. 24, 2012

Re: [Esug-list] GSoC - Package management with Fuel

by Nicolás Paez

Great work!!! Congrats. Saludos! NicoPaez <http://nicopaez.wordpress.com/> On Fri, Aug 24, 2012 at 5:01 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi > > This week has ended Google Summer of Code program 2012. I have to > thank Marcus and Carlos Ferro, my mentors, as well as Mariano, > Guille Polito, Camillo Bruni, and others, who collaborated in > different ways during these three months. Also thank, of course, > to Carla and Janko... and Google ;) > > The main purpose of this mail is to summarize the work done for my > project, named "Package management with Fuel" [1][2]. > > Tools for managing code in Pharo export classes, traits, and methods > as series of source definitions, which then import by evaluating them > with the compiler. This is basically how FileOut/FileIn or Monticello > works. This is slow on large pieces of code, so if you want to install > a big package, you need a lot of time compiling it. Why should you > compile it again, given that it was all compiled when you exported the > package? The bytecodes will be the same again, you know... If you just > could load the Classes and Compiled Methods instead of compiling it > all again, you can save time. > > With this goal in mind, I started working in FuelPackageLoader[4] (now > Tanker[3]), a prototype we wrote last year, which already exports and > imports packages without using any compiler. But it has two important > issues: it wasn't capable of export source code, and it wasn't able to > tolerate class-shape changes in hierarchies (ie, a change on inst vars > in a external superclass). So, we decided to start from scratch with a > new prototype, code name Carbono. The idea was to reify how FileOut > and FileIn are done, but storing binary information so that > compilation can be avoided. > > In a nutshell, Carbono stores a package into two files: > - A sources file, imitating the traditional FileOut chunk format. > - A binary file, where uses Fuel[5] to serialize a series of code > definitions. Each of them knows the position in the sources file where > its source code counterpart is. For example, a class definition knows > the position of its comment (in the case it exists), and a method > definition knows the position of its source code. > > A basic example, to export a couple of classes: > > TAExport new > binariesOn: aBinaryStream > sourcesOn: aTextStream; > behaviors: {ClassA. ClassB}; > methods: {}; > initializeClasses: true; > run. > > which then you can import with: > > TAImport new > binariesFrom: aBinaryStream > sourcesFrom: aTextStream; > run. > > Anyway, you can also choose to: > - export only binaries or only sources > - import only binaries (source code can be decompiled) > - import only sources (via #fileIn) > > Mariano Martinez Peck worked a lot on it, fixing bugs, and especially > optimizing it A LOT, so I hope you will enjoy his demonstration this > Monday on ESUG Innovation Awards. Seems that he could export Seaside, > Pier and Magritte, and import them in another image, with source code, > and just in a few seconds ;) Also, some ultra confidential WikiLeaks > revealed that he could export almost all Pharo packages, and import > them in a kernel image, all with source codes but without using the > compiler :) > > Note1: Tolerating class-shape changes in hierarchies is not yet done, > but it should in some days. So far, the only strategy when a change is > detected will be to recompile methods, but it may be more > sophisticated in a not-so-far future. > > Note2: Although finally it was not strictly necessary, Guillermo > Polito and me wrote tests for a new ClassBuilder. It is part of Slot, > a kind of reification of objects layout made by Toon Verwaest and > Camillo Bruni. It is too long to explain it here, but the thing is > that was not an easy job, and we hope it will be integrated in Pharo. > > This is a work in progress, but you can install and try it on latest > Pharo 2.0, evaluating: > > Gofer it > squeaksource3: 'PharoTaskForces'; > package: 'Slot'; > package: 'SlotTests'; > load. > (Smalltalk at: #SlotVirus) perform: #spread. > Gofer it > squeaksource3: 'PharoTaskForces'; > package: 'SlotsClassBuilderIntegration'; > load. > Gofer new > smalltalkhubUser: 'marianopeck' project: 'Tanker'; > package: 'ConfigurationOfTanker'; > load. > (Smalltalk at: #ConfigurationOfTanker) loadBleedingEdge. > Gofer new > squeaksource: 'FuelExperiments'; > package: 'Carbono'; > package: 'CarbonoTests'; > load. > > Cheers, > Martín > > [1]: http://gsoc2012.esug.org/projects/fuel-packages > [2]: > https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2012/tin… > [3]: > http://marianopeck.wordpress.com/2012/08/11/tanker-transporting-packages-wi… > [4]: > http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… > [5]: http://rmod.lille.inria.fr/web/pier/software/Fuel > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >

Aug. 24, 2012

PhD topics with RMOD

by Stéphane Ducasse

Hi guys we have a position for a PhD. If you are interested we can talk at ESUG 2012 or by Skype. Stef Context: Dynamically-typed languages cannot take advantage of static type information. In this context we would like to study the benefit of the introduction of static types *annotations* on library design and general robustness. The benefits can be at the level of the robustness (bug identification), but also tools (IDE) and support for assembly generation/c in case of JIT. The PhD grant is financed in the context of the Safe Python project therefore the Ph.D. will have to work in contact do we with the project partners and help in the context of some deliverables. The following tasks have to be done: - RPython is not formally defined. One of the first task will be to define the formal semantic of RPython. One approach is to write a RPython interpreter based on an operational semantics and to compare the output with the RPython interpreter. We will certainly use PLT redex which is a domain-specific language to specify and debug operational semantics. - We may use the abstract syntax tree of PyLint and use the Frama-C infrastructure. We will also consider to build a Python parser based on petitParser. - Define of some default metrics may also be necessary for the SafePython project. Their definition should be trivial on ASTs. - Analysis of the benefits of static typing for RPython. One idea is to study the existing python libraries and analyze the "distance" to the RPython subset. - Exploring type checking in presence of inconsistent type annotations. - Since we are developing Pharo and that static type annotation are important to support C or assembly generation, we would like to apply the same technique to Pharo: - define a syntax to support type annotation (reuse the one developed by Pleaid team member) - perform some analysis of existing library. References [1] D. Ancona, M. Ancona, A Cuni, and N. Matsakis. RPython: a Step Towards Reconciling Dynamically and Statically Typed OO Languages. In OOPSLA 2007 Proceedings and Companion, DLS'07: Proceedings of the 2007 Symposium on Dynamic Languages, pages 53-64. ACM, 2007. [2] A Visual Environment for Developing Context-Sensitive Term Rewriting Systems Jacob Matthews, Robert Bruce Findler, Matthew Flatt, and Matthias Felleisen [3] Felleisen,M.,Hieb,R.:The revised report on the syntactic theories of sequential control and state. (1992) 235–271 Skills and Profile You must hold a Master's in computer science, control engineering, mathematics, scientific computation or an equivalent diploma. Nationality is not taken into consideration. Knowledge in programming language design. Object-oriented programming with knowledge of Smalltalk and Python are a plus. About Lille and INRIA: Lille is located in the north of france at the border to Belgium one hour from Paris, 1h20 from London, 35 min from Brussels, by train. French food, combined with belgian beer. RMoD: http://rmod.lille.inria.fr INRIA Lille: http://www.inria.fr/lille/ INRIA in General: http://www.inria.fr Lille: http://en.wikipedia.org/wiki/Lille http://wikitravel.org/en/Lille Benefits/Users/ducasse/Workspace/FirstCircle/Administration/Ad-INRIA/Projects/2012-SafePython/PhDtopics.txt Duration : 36 months – starting date of the contract : October 2012, 15th Salary: 1957,54 EUR the first two years and 2058,84 EUR the third year Monthly salary after taxes: around 1597,11 EUR the 1st two years and 1679,76 EUR the 3rd year (social security included). Possibility of French courses Help for housing Scientific Resident card and help for husband/wife visa Additional Information Application deadline: 15 September 2012 Contact for position: stephane.ducasse(a)inria.fr

Aug. 24, 2012

GSoC - Package management with Fuel

by Martin Dias

Hi This week has ended Google Summer of Code program 2012. I have to thank Marcus and Carlos Ferro, my mentors, as well as Mariano, Guille Polito, Camillo Bruni, and others, who collaborated in different ways during these three months. Also thank, of course, to Carla and Janko... and Google ;) The main purpose of this mail is to summarize the work done for my project, named "Package management with Fuel" [1][2]. Tools for managing code in Pharo export classes, traits, and methods as series of source definitions, which then import by evaluating them with the compiler. This is basically how FileOut/FileIn or Monticello works. This is slow on large pieces of code, so if you want to install a big package, you need a lot of time compiling it. Why should you compile it again, given that it was all compiled when you exported the package? The bytecodes will be the same again, you know... If you just could load the Classes and Compiled Methods instead of compiling it all again, you can save time. With this goal in mind, I started working in FuelPackageLoader[4] (now Tanker[3]), a prototype we wrote last year, which already exports and imports packages without using any compiler. But it has two important issues: it wasn't capable of export source code, and it wasn't able to tolerate class-shape changes in hierarchies (ie, a change on inst vars in a external superclass). So, we decided to start from scratch with a new prototype, code name Carbono. The idea was to reify how FileOut and FileIn are done, but storing binary information so that compilation can be avoided. In a nutshell, Carbono stores a package into two files: - A sources file, imitating the traditional FileOut chunk format. - A binary file, where uses Fuel[5] to serialize a series of code definitions. Each of them knows the position in the sources file where its source code counterpart is. For example, a class definition knows the position of its comment (in the case it exists), and a method definition knows the position of its source code. A basic example, to export a couple of classes: TAExport new binariesOn: aBinaryStream sourcesOn: aTextStream; behaviors: {ClassA. ClassB}; methods: {}; initializeClasses: true; run. which then you can import with: TAImport new binariesFrom: aBinaryStream sourcesFrom: aTextStream; run. Anyway, you can also choose to: - export only binaries or only sources - import only binaries (source code can be decompiled) - import only sources (via #fileIn) Mariano Martinez Peck worked a lot on it, fixing bugs, and especially optimizing it A LOT, so I hope you will enjoy his demonstration this Monday on ESUG Innovation Awards. Seems that he could export Seaside, Pier and Magritte, and import them in another image, with source code, and just in a few seconds ;) Also, some ultra confidential WikiLeaks revealed that he could export almost all Pharo packages, and import them in a kernel image, all with source codes but without using the compiler :) Note1: Tolerating class-shape changes in hierarchies is not yet done, but it should in some days. So far, the only strategy when a change is detected will be to recompile methods, but it may be more sophisticated in a not-so-far future. Note2: Although finally it was not strictly necessary, Guillermo Polito and me wrote tests for a new ClassBuilder. It is part of Slot, a kind of reification of objects layout made by Toon Verwaest and Camillo Bruni. It is too long to explain it here, but the thing is that was not an easy job, and we hope it will be integrated in Pharo. This is a work in progress, but you can install and try it on latest Pharo 2.0, evaluating: Gofer it squeaksource3: 'PharoTaskForces'; package: 'Slot'; package: 'SlotTests'; load. (Smalltalk at: #SlotVirus) perform: #spread. Gofer it squeaksource3: 'PharoTaskForces'; package: 'SlotsClassBuilderIntegration'; load. Gofer new smalltalkhubUser: 'marianopeck' project: 'Tanker'; package: 'ConfigurationOfTanker'; load. (Smalltalk at: #ConfigurationOfTanker) loadBleedingEdge. Gofer new squeaksource: 'FuelExperiments'; package: 'Carbono'; package: 'CarbonoTests'; load. Cheers, Martín [1]: http://gsoc2012.esug.org/projects/fuel-packages [2]: https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2012/tin… [3]: http://marianopeck.wordpress.com/2012/08/11/tanker-transporting-packages-wi… [4]: http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-package… [5]: http://rmod.lille.inria.fr/web/pier/software/Fuel

Aug. 24, 2012

Re: [Esug-list] Dinner in Ghent on Friday

by Sean P. DeNigris

I'm getting in Friday morning... should work... -- View this message in context: http://forum.world.st/Dinner-in-Ghent-on-Friday-tp4645064p4645115.html Sent from the ESUG mailing list archive at Nabble.com.

Aug. 23, 2012

Dinner in Ghent on Friday

by David Chisnall

Hi, Is anyone around on Friday for dinner? A couple of us are planning on leaving the Ibis Gent Opera at 7:30pm in search of food. David

Aug. 23, 2012

Pharo usage poll

by Esteban Lorenzano

Hi, sorry for multiple posts I'm running a small survey about Pharo usage... it is just to collect some minor data, not big answers, just some :) If you don't use Pharo... please ignore it. If you already answered... ignore it as well. But if you use Pharo and still didn't answer, please go to: https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dFZKeXU… and answer it... they are just 3 questions! Thanks, Esteban

Aug. 22, 2012