March 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

March 2, 2016

Call for Papers: 11th Workshop on Implementation, Compilation, Optimization of OO Languages, Programs and Systems

by Stefan Marr

Call for Papers: ICOOOLPSâ16 ============================ 11th Workshop on Implementation, Compilation, Optimization of OO Languages, Programs and Systems Co-located with ECOOP July 18, 2016, Rome, Italy URL: http://2016.ecoop.org/track/ICOOOLPS-2016 Twitter: @ICOOOLPS The ICOOOLPS workshop series brings together researchers and practitioners working in the field of language implementation and optimization. The goal of the workshop is to discuss emerging problems and research directions as well as new solutions to classic performance challenges. The topics of interest for the workshop include techniques for the implementation and optimization of a wide range of languages including but not limited to object-oriented ones. Furthermore, meta-compilation techniques or language-agnostic approaches are welcome, too. A non-exclusive list of topics follows: - implementation and optimization of fundamental languages features (from automatic memory management to zero-overhead metaprogramming) - runtime systems technology (libraries, virtual machines) - static, adaptive, and speculative optimizations and compiler techniques - meta-compilation techniques and language-agnostic approaches for the efficient implementation of languages - compilers (intermediate representations, offline and online optimizations,...) - empirical studies on language usage, benchmark design, and benchmarking methodology - resource-sensitive systems (real-time, low power, mobile, cloud) - studies on design choices and tradeoffs (dynamic vs. static compilation, heuristics vs. programmer input,...) - tooling support, debuggability and observability of languages as well as their implementations ### Workshop Format and Submissions This workshop welcomes the presentation and discussion of new ideas and emerging problems that give a chance for interaction and exchange. More mature work is welcome as part of a mini-conference format, too. We aim to interleave interactive brainstorming and demonstration sessions between the formal presentations to foster an active exchange of ideas. The workshop papers will be published either in the ACM DL or in the Dagstuhl LIPIcs ECOOP Workshop proceedings. Until further notice, please use the ACM SIGPLAN template with a 10pt font size: http://www.sigplan.org/Resources/Author/ - position and work-in-progress paper: 1-4 pages - technical paper: max. 10 pages - demos and posters: 1-page abstract For the submission, please use the HotCRP system: http://ssw.jku.at/icooolps/ ### Important Dates - abstract submission: April 11, 2016 - paper submission: April 15, 2016 - notification: May 13, 2016 - all deadlines: Anywhere on Earth (AoE), i.e., GMT/UTCâ12:00 hour - workshop: July 18th, 2016 ### Program Committee Edd Barrett, Kingâs College London, UK Clement Bera, Inria Lille, France Maxime Chevalier-Boisvert, UniversitÃ© de MontrÃ©al, Canada Tim Felgentreff, Hasso Plattner Institute, Germany Roland Ducournau, LIRMM, UniversitÃ© de Montpellier, France Elisa Gonzalez Boix, Vrije Universiteit Brussel, Belgium David Gregg, Trinity College Dublin, Ireland Matthias Grimmer, Johannes Kepler University Linz, Austria Michael Haupt, Oracle, Germany Richard Jones, University of Kent, UK Tomas Kalibera, Northeastern University, USA Hidehiko Masuhara, Tokyo Institute of Technology, Japan Tiark Rompf, Purdue University, USA Jennifer B. Sartor, Ghent University, Belgium Sam Tobin-Hochstadt, Indiana University, USA ### Workshop Organizers Stefan Marr, Johannes Kepler University Linz, Austria Eric Jul, University of Oslo, Norway For questions or concerns, please mail to stefan.marr at jku.at or contact us via https://twitter.com/icooolps.

March 2, 2016

Re: [Pharo-dev] Pharo Days 2016 Registration is open

by phil＠highoctane.be

registered :-) On Wed, Mar 2, 2016 at 9:38 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Registration for the Pharo Days 2016 is now open ! > > We are using EventBrite. You can buy tickets using PayPal and any credit > card. If absolutely necessary, you can opt for an off line payment. Please > register on time. > > http://www.eventbrite.com/e/pharo-days-2016-tickets-22454533113 > > For social registration you can use Doodle. > > http://doodle.com/poll/rsc86cqzxbgwr9tr > > Spread the word: http://pharodays2016.pharo.org. >

March 2, 2016

Pharo Contributors & Consultants

by Peter UhnÃ¡k

Hi all, we are currently updating the pages for Pharo Contributors and Consultants. https://consultants.pharo.org/ and https://contributors.pharo.org/ if you want to add or update your record (info, mail, image, ...), you can do so by sending us a pull request on GitHub in the appropriate repository the format is STON so it should be understandable. Contributors: https://github.com/pharo-project/pharo-project-contributors Consultants: https://github.com/pharo-project/pharo-project-consultants Alternatively you can open an issue in the github issue tracker with the new info and it will be handled. Peter

March 2, 2016

Pharo Days 2016 Registration is open

by Sven Van Caekenberghe

Registration for the Pharo Days 2016 is now open ! We are using EventBrite. You can buy tickets using PayPal and any credit card. If absolutely necessary, you can opt for an off line payment. Please register on time. http://www.eventbrite.com/e/pharo-days-2016-tickets-22454533113 For social registration you can use Doodle. http://doodle.com/poll/rsc86cqzxbgwr9tr Spread the word: http://pharodays2016.pharo.org.

March 2, 2016

Can't enter Square Brackets in new images

by Udo Schneider

All, I'm currently chasing a strange problem with new 5.0 based Images. In the regular Pharo 5.0 Beta Image and current Moose (5.1) Image you can't enter square brackets anymore. It seems to change the class/category/method selection in Nautilus and causes a non-breakable loop of discarding/ignoring/saving the changes dialog for changed methods... Checking the same VM with older 5.0 images works w/o any problem. So I assume an image problem - not a VM problem. Has anyone seen this? I'm currently testing on Mac OS X with a german keyboard and US-English locale. Will test on Windows tomorrow. CU, Udo Pharo 5.0 Details: Smalltalk image version. "'Pharo5.0'" SystemVersion current imageVersionString. "'Pharo-5.0-50622-'" Smalltalk vm version. "'CoInterpreter * VMMaker.oscog-rmacnak.1586 uuid: 8e44b2a7-68ee-4fc9-8513-a04520267053 Dec 13 2015 StackToRegisterMappingCogit * VMMaker.oscog-rmacnak.1586 uuid: 8e44b2a7-68ee-4fc9-8513-a04520267053 Dec 13 2015 https://github.com/estebanlm/pharo-vm.git Commit: 6dc730123e8f2b0327839b235d16e0604a92288e Date: 2015-12-13 00:23:41 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #456 '" Moose Details: Smalltalk image version. "'Pharo5.0'" SystemVersion current imageVersionString. "'Pharo-5.0-50622-'" Smalltalk vm version. "'CoInterpreter * VMMaker.oscog-rmacnak.1586 uuid: 8e44b2a7-68ee-4fc9-8513-a04520267053 Dec 13 2015 StackToRegisterMappingCogit * VMMaker.oscog-rmacnak.1586 uuid: 8e44b2a7-68ee-4fc9-8513-a04520267053 Dec 13 2015 https://github.com/estebanlm/pharo-vm.git Commit: 6dc730123e8f2b0327839b235d16e0604a92288e Date: 2015-12-13 00:23:41 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #456 '"

March 1, 2016

Re: [Pharo-dev] MemoryFileSystemFile>>#readStream forces String

by Sven Van Caekenberghe

using #asString there is wrong, IMHO, if the memory stream is on bytes it should return a read stream reading bytes, if it is on characters, the read stream should return characters. > On 01 Mar 2016, at 21:13, Max Leske <maxleske(a)gmail.com> wrote: > > >> On 01 Mar 2016, at 20:51, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: >> >> On 29/02/16 23:06, Sven Van Caekenberghe wrote: >>> I think it is not good to do this, better stick with bytes. >> Should I fix it and submit a slice or use a workaround in my code? > > I donât think it makes sense to change #readStream. I do think though, that the tools would profit from an improved XML handling. > > Max > >> >> CU, >> >> Udo >> >> >> >> > >

March 1, 2016

Re: [Pharo-dev] MemoryFileSystemFile>>#readStream forces String

by Max Leske

> On 01 Mar 2016, at 20:51, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: > > On 29/02/16 23:06, Sven Van Caekenberghe wrote: >> I think it is not good to do this, better stick with bytes. > Should I fix it and submit a slice or use a workaround in my code? I donât think it makes sense to change #readStream. I do think though, that the tools would profit from an improved XML handling. Max > > CU, > > Udo > > > >

March 1, 2016

Re: [Pharo-dev] MemoryFileSystemFile>>#readStream forces String

by Udo Schneider

On 29/02/16 23:06, Sven Van Caekenberghe wrote: > I think it is not good to do this, better stick with bytes. Should I fix it and submit a slice or use a workaround in my code? CU, Udo

March 1, 2016

[Issue tracker] Please check old issues to prepare for release!

by Marcus Denker

Hello, As you might now, we are in the process of getting Pharo5 stable for a release. One of the things that is always important is to clean the issue tracker: over the year that the new release in in development, lots of issue accumulate. Please, just for the issue you have either opened yourself or where you have been involved in the discussion: -> Is the issue still relevant? Maybe it has been fixed? -> Is it really important to stay open? Sometimes things are just not worth itâ¦ -> Is this really an issue tracker entry? What I mean here is that an issue tracker is not a wish-list. There are so many things I want, but adding an issue is often not helping. âIt would be nice ifââ¦ -> Bugs: Can it be reproduced? How? -> Features: We are in freeze. Likely it should be moved to the âPharo 6â Milestone. We are at 521 open issue as of now, I am sure we can get that number down till we release. At some point (soon) we will make a real âshow stopperâ list for the issue that we have to fix before we can release. Marcus

March 1, 2016