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

[Pharo-project] pharo-2.0-tests Â» mac - Build # 390 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 4, 2012

Re: [Pharo-project] Call for PhD candidates in the Software Composition Group, U Bern

by Alexandre Bergel

Spring is coming in South America. PhD positions are also available in Chile. The keywords that are close to what we are doing are: software engineering, Pharo, visualization, profiling, debugging, testing Contact me for more information. cheers, Alexandre On Oct 4, 2012, at 7:50 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I join also our current position :) > >>> Title: Optional Static Types for Dynamic Languages >>> >>> Context: Dynamically-typed languages cannot take advantage of static >>> type information. In this context we would like to study the benefits >>> of introducing static type annotations on library design, general >>> robustness and tooling. The benefits will be at the level of >>> robustness (bug >>> identification), tools (IDE), and support for assembly/c generation >>> in >>> case of static compilation. >>> >>> The Ph.D. grant is financed in the context of the Safe Python >>> project. >>> In this context the Ph.D. student will have to work in contact with >>> the project partners and help in the context of some deliverables. >>> >>> The student will: >>> >>> - compare existing static subsets of dynamic languages; >>> - formally define the semantics of RPython (this is one >>> deliverables of the project); >>> - analyze the benefits of static typing for existing Python and >>> Pharo code; >>> - explore type checking in presence of incomplete or inconsistent >>> type annotations. >>> >>> Some possible paths for the student: >>> >>> - studying the existing python libraries and analyzing the >>> "distance" to the RPython subset; >>> - using PLT redex which is a domain-specific language to specify >>> and >>> debug the operational semantics; >>> - using the abstract syntax tree of PyLint and use the Frama-C >>> infrastructure; >>> - building a Python parser based on PetitParser. >>> >>> Since we are developing Pharo and that static type annotations is >>> important to support C or assembly generation, we would like to apply >>> the same techniques to Pharo through: >>> >>> - building on top of existing work done in the context of the >>> Gradual Types >>> project of PLEIAD; >>> - the development of some tools; >>> - the analysis of existing libraries. >>> >>> 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: >>> >>> The student 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 is required. >>> 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 >>> >>> 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 >>> Contact information: stephane.ducasse(a)inria.fr and >>> marcus.denker(a)inria.fr >>> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 4, 2012

Re: [Pharo-project] Call for PhD candidates in the Software Composition Group, U Bern

by StÃ©phane Ducasse

Hi I join also our current position :) >> Title: Optional Static Types for Dynamic Languages >> >> Context: Dynamically-typed languages cannot take advantage of static >> type information. In this context we would like to study the benefits >> of introducing static type annotations on library design, general >> robustness and tooling. The benefits will be at the level of >> robustness (bug >> identification), tools (IDE), and support for assembly/c generation >> in >> case of static compilation. >> >> The Ph.D. grant is financed in the context of the Safe Python >> project. >> In this context the Ph.D. student will have to work in contact with >> the project partners and help in the context of some deliverables. >> >> The student will: >> >> - compare existing static subsets of dynamic languages; >> - formally define the semantics of RPython (this is one >> deliverables of the project); >> - analyze the benefits of static typing for existing Python and >> Pharo code; >> - explore type checking in presence of incomplete or inconsistent >> type annotations. >> >> Some possible paths for the student: >> >> - studying the existing python libraries and analyzing the >> "distance" to the RPython subset; >> - using PLT redex which is a domain-specific language to specify >> and >> debug the operational semantics; >> - using the abstract syntax tree of PyLint and use the Frama-C >> infrastructure; >> - building a Python parser based on PetitParser. >> >> Since we are developing Pharo and that static type annotations is >> important to support C or assembly generation, we would like to apply >> the same techniques to Pharo through: >> >> - building on top of existing work done in the context of the >> Gradual Types >> project of PLEIAD; >> - the development of some tools; >> - the analysis of existing libraries. >> >> 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: >> >> The student 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 is required. >> 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 >> >> 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 >> Contact information: stephane.ducasse(a)inria.fr and >> marcus.denker(a)inria.fr >> >

Oct. 4, 2012

[Pharo-project] Call for PhD candidates in the Software Composition Group, U Bern

by Oscar Nierstrasz

Applications are invited for PhD candidates at the Software Composition Group, University of Bern, Switzerland, to contribute to the SNSF project "Agile Software Assessment". The Software Composition Group carries out research in software analysis and programming language design and implementation, with a view to enabling software evolution. The SCG is led by Prof. Oscar Nierstrasz and is part of the Institute of Computer Science and Applied Mathematics (IAM) at the University of Berne. Details about the research project can be found here: http://scg.unibe.ch/research/snf13 The candidate must have a MSc in Computer Science (equivalent to a Swiss MSc), should demonstrate strong programming skills, and have research interests in several of the following areas: - software evolution - program understanding - software modeling - model-driven engineering - reverse engineering - domain specific languages - dynamic analysis - integrated development environments - programming language design - virtual machine technology To apply, please send an email including your CV to Prof. Oscar Nierstrasz (oscar(a)iam.unibe.ch) --- Prof. Dr. O. Nierstrasz -- oscar(a)iam.unibe.ch Software Composition Group -- http://scg.unibe.ch/oscar University of Bern -- Tel/Fax +41 31 631.4618/3355

Oct. 4, 2012

Re: [Pharo-project] NB cant locate a module

by StÃ©phane Ducasse

> >> Ok, so the plot thickens! thanks for the info Igor >> >> I will follow your guideliness, and try to make Pango work >> as you did with Cairo. >> > good luck with that, right now i working making it work on Windows . > >> Fernando >> pd: I also HATE all this non-smalltalk crap! So thanks for the blog and effort. Believe us we hate that too. Stef

Oct. 4, 2012

Re: [Pharo-project] Pharo Sprint Nov 2

by StÃ©phane Ducasse

We should probably reserve the large meeting room downstair (they call it conseil for bat B) because I do not know if we will be able to use the open space. Stef On Oct 3, 2012, at 2:08 PM, Marcus Denker wrote: > > On Oct 3, 2012, at 2:00 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 03 Oct 2012, at 13:13, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> RMoD is organizing a Pharo Sprint >>> >>> - When? Fr, Nov 2nd. Starting at 9am >>> - Where? INRIA Lille: http://www.inria.fr/centre/lille >> >> And do we get to visit your shiny new building/offices ? > > > Yes, I think we will do it here in the meeting room / open space. > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > >

Oct. 4, 2012

[Pharo-project] Fwd: [fossa] SAVE THE DATE! 4, 5 and 6th of December 2012 at EuraTechnologies , Lille, France

by Marcus Denker

Hi, There will be an Open Source Conference in Lille beginning of December. This will be at Euratechnologies: http://www.rudebaguette.com/2012/07/10/euratechnologies/ We are planning to do a Pharo Workshop. Marcus Begin forwarded message: > From: Stephane Ribas <stephane.ribas(a)inria.fr> > Subject: [fossa] SAVE THE DATE! 4,5 and 6th of December 2012 at EuraTechnologies , Lille, France > Date: October 4, 2012 9:30:56 AM GMT+02:00 > To: fossa(a)inria.fr > > French text below (worth reading it!), > > Dear all, bonjour Ã tous, > > Inria and EuraTechnologies are happy to announce you the fOSSa 2012 Edition! > fOSSa conference will take place on the 4,5, 6th December 2012 in Lille, France. > > Thanks to the quality of our speakers & attendees, thanks to our open & pragmatic approach, more than 250 people came each year; more than 100 articles in the press & webzines talk positively about the conference content... fOSSa conference is playing a predominant role in the OSS arena year after year. > > This year, the conference will address: > - Education (Resp. Ivaylo Ganchez) > - IRILL (Resp. Roberto Di Cosmo) > - History of the Free Software/Open Source mouvement (Resp. Christophe Masutti & Alexis Kaufmann) > - Movie: 'Revolution OSâ (wonderful movie! open to a large public) > - Digital Native Generation (Resp. Stephane Frenot & Stephane Grumbach) > - Openness: Open Arts and Open Hardware (Resp. JÃ©rome Copin) > - Licences: No lawers, No councels, only return on experience (Resp. Gabriele Ruffatti) > - Communities: Community management has never been so easy (Resp. Stephane Ribas) > - Workshops: Many code developement training sessions are scheduled -> Gnome, Mozilla, LibreOffice, Pharo, SpagoBI, etc. > > Each topic will end up with a debate (What are the issues that faces OSS today, What about data concentration made in the US & China, What are the good practices in Licencing...) > > We will send more news about the organisation and progress of the conference very soon; > This edition includes talks from great (and rare) speakers ... we keep the names ... for the moment... secret :-) > > So SAVE THE DATE ! > 4,5 and 6th of December 2012 at EuraTechnologies, Lille, France > > fOSSa program and organisation committee members are Engineering Group, Framasoft, Insa Lyon, Mairie de Lille, and University of Paris 8. > fOSSa is sponsored by HP. > fOSSa registrations are free :-) > fOSSa Website: http://fossa.inria.fr > > > > -- En franÃ§ais dans le texte > Bonjour Ã tous, > > Inria et EuraTechnologies sont heureux de vous annoncer la tenue prochaine de lâÃ©dition 2012 des confÃ©rences fOSSa qui se tiendront les 4, 5 et 6 dÃ©cembre 2012 Ã Lille, France. > > La qualitÃ© de nos intervenants et de notre auditoire, lâoriginalitÃ© de notre approche et les thÃ©matiques abordÃ©es Ã fOSSa, font venir chaque annÃ©e plusieurs centaines de passionnÃ©s et des figures de lâopen source ; La trÃ¨s large couverture de fOSSa par la presse et les webzines est probablement dÃ» au caractÃ¨re atypique de fOSSa qui offre Ã la fois la convivialitÃ© dâun Ã©vÃ©nement de taille humaine et qui attire de grandes figures de lâopen source. Câest la dynamique de cette communautÃ© qui permet Ã fOSSa de jouer, dâune Ã©dition Ã la suivante, un rÃ´le prÃ©dominant dans lâarÃ¨ne de lâopen source. > > Cette annÃ©e, nous reviendrons aux racines de lâopen source : dÃ©veloppement, recherche, communautÃ©s. fOSSa 2012 abordera : > > - lâenseignement (Resp. Ivaylo Ganchez) > > - IRILL (Resp. Roberto Di Cosmo) > > - lâHistoire du logiciel libre et de lâopen source : Resp. Christophe Masutti & Alexis Kaufmann > > - Projection du film Revolution OS : un documentaire passionnant sur lâopen source. Cette sÃ©ance sera ouverte au public, > > - Digital Native Generation : (Resp. StÃ©phane Frenot & StÃ©phane Grumbach) > > - Openness : Open Arts and Open Hardware (Resp. JÃ©rome Copin) > > - Licences : pas de juristes, pas de consultants, rien que des tÃ©moignages et des retours dâexpÃ©rience (Resp. Gabriele Ruffatti) > > - Communities : le community management pour les nuls ! (Resp. Stephane Ribas) > > - Workshops : plein dâateliers intÃ©ressants au programme -> Gnome, Mozilla, LibreOffice, Pharo, SpagoBI, etc. > > Chaque thÃ¨me se termine sur un dÃ©bat : quels sont les problÃ¨mes que rencontre lâopen source en ce moment, quelles sont les implications de la concentration de donnÃ©es pratiquÃ© par les USA et la Chine, quelles sont les bonne pratique en matiÃ¨re de choix de licence, et plein dâautres questions intÃ©ressantes, y compris les votres ! > > Nous diffuserons trÃ¨s bientÃ´t dâautres informations sur lâorganisation et le dÃ©roulement des confÃ©rences ; Ce que nous pouvons dÃ©jÃ dire câest que, comme dâhabitude lâÃ©dition 2012 rassemblera du beau monde, et rÃ©servera aussi quelques surprises, notamment des interventions de grands nomsâ¦ que nous gardons secrets pour le moment ! > > Alors pensez Ã rÃ©servez les 4, 5 et 6 dÃ©cembre 2012 Ã Euratechnologie , Lille, France. > > Les membres du comitÃ© de programme et dâorganisation de fOSSa sont Engineering Group, Framasoft, lâInsa de Lyon, la Mairie de Lille, et lâUniversitÃ© de Paris 8. > > fOSSa est sponsorisÃ© par Hewlett Packard. > > Venez trouver dâautres informations sur http://fossa.inria.fr > > fOSSa program and organisation committee members are Engineering Group, Framasoft, Insa Lyon, Mairie de Lille, and University of Paris 8. > fOSSa is sponsored by HP. > fOSSa registrations are free :-) > fOSSa Website: http://fossa.inria.fr > [%|loc%]To unsubscribe:[%END%] [% conf.wwsympa_url %]/auto_signoff/[% list.name %]/[% user.email %] -- Marcus Denker -- http://marcusdenker.de

Oct. 4, 2012

Re: [Pharo-project] To try out FileSystem in 2.0 -- which download?

by Marcus Denker

On Oct 4, 2012, at 9:22 AM, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: > i love they manner in which you summarized more then 10 years of > struggles, and introduce the high hopes that this future beholds... > The future will be great! I am quite sure that we will be amazed ourselves in 5 years. It will be a completely non-linear experience... :-) Marcus -- Marcus Denker -- http://marcusdenker.de

Oct. 4, 2012

[Pharo-project] [update 2.0] #20320

by Marcus Denker

20320 ----- Issue 6757: Nuke HTTPClient and HTTPSocket and deprecated ZnHTTPSocketFacade http://code.google.com/p/pharo/issues/detail?id=6757 Remove HTTPClient completely. Remove all methods from HTTPSocket, instance and class side, as well as all instance and class variables. Keep the methods on the class side delegating to ZnHTTPSocketFacade as they constitute a working API that might be used by legacy code. Deprecate all class side methods on HTTPSocket that were delegating to ZnHTTPSocketFacade, as defined by the special Zinc-Patch-HTTPSocket package. Remove HTTPSocketTests ================================================================================= Thanks Sven! -- Marcus Denker -- http://marcusdenker.de

Oct. 4, 2012

Re: [Pharo-project] To try out FileSystem in 2.0 -- which download?

by Fernando Olivero

i love they manner in which you summarized more then 10 years of struggles, and introduce the high hopes that this future beholds... thanks Marcus! Fernando On Thu, Oct 4, 2012 at 9:16 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Thanks for the explanation and pointers, Marcus. > > Well written, well said, as usual ;-) > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > On 04 Oct 2012, at 08:26, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On Oct 4, 2012, at 8:02 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> Now there are two philosophies >>> >>> 1) we load the new in addition. It even is compatible to many different versions of the System, and everyone uses it >>> in new code. But the sytem can not use it, as the developer of course wants to load the latest version of this independendly >>> develpopped library. Some people requested that for FileSystem, and we renamed all classes so that they can continue >>> to load the code themselves. >> >> This actually is interesting, these two philosophies... >> >> 1) The Addition View >> >> Smalltalk is perfect and finished. Everything we do we do "on top". If we implement Morphic, we keep MVC. Things like >> FileSystem code is there as an additonal library. >> When doing research, the picture you have is not that of a System that you improve to make a new System that makes >> the next research easier. No. You do something *on top*, and throw it away after. >> >> 2) The System View >> >> I think some people's brain kind of got a hickup when they looked at instances of Class and saw that they just use standard >> libraries. MethodDictionay is a Dictionary... there is no special "I wrote everyhting again because I am clever!" code >> even deep in the system. That is one of the things that makes Smalltalk powerful! >> >> The main reason is that it created a feedback loop: We improve something for an application. But then, instead of throwing >> it away, we *apply* that improvement to the *whole* system. The system gets better (faster, smaller). And its expressiveness >> is improved: the next developer can just *use* the improvement and put the time into something else. >> >> Especially in Research, this is quite important: You can't publish things that have already been done. Time is limited (just 3-4 years >> to do a PhD...). So if the guy has to constantly start from scratch, this gets very hard after just some interations. Yet, when the System >> itself improves... the picture here is that of a mountain: We can always climb up from the valley deep down, or we can build base camps. >> Who will do better? >> >> I think we are starting to (slowly) see this with Pharo. E.g. the on-demand loading of the .sources. It uses Zinc and FileSystem, it's just a >> couple of lines of code. Yes, you could have done it before. But would anyone do it? Of course not. (just a very trivial example). >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > >

Oct. 4, 2012