- Pharo-dev - lists.pharo.org

FileSystem fix integration
by Stephane Ducasse Aug. 17, 2017

Aug. 17, 2017

Hi alistair I will go over all the FS changes and push them in Pharo 70. I'm learning the process to integrate fixes and I attract bugs :) Stef

4 23

Is there some RSS parser updated around?
by Mariano Martinez Peck Aug. 16, 2017

Aug. 16, 2017

Hi guys, All the RSS parsers I found are all quite outdated...does someone have an updated one? I want to parse RSS and then display it within Seaside (to render kind of company news). Thanks in advance, -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo 70 ] build 39 - PR 210 20165/Support-segment-path-printing
by Stephane Ducasse Aug. 16, 2017

Aug. 16, 2017

https://pharo.fogbugz.com/f/cases/20165/Support-segment-path-printing https://github.com/pharo-project/pharo/pull/210 one more :)

1 0

File & Socket Handle Access
by Eliot Miranda Aug. 16, 2017

Aug. 16, 2017

Hi All, recently Denis Kudriashov wanted to access the OS handle of a Socket from the image to pass through the FFI. David Lewis pointed out that the AioPlugin provides a primitive to do this. I asked David why he didn't add it to the SocketPlugin in the first place and he discussed Andreas Rabb's security concerns. It strikes me a) that accessing the OS handle of a file or a socket is extremely useful in some circumstances and invalid in others b) having handle access in a secondary plugin is inconvenient to say the least c) having access only to Socket handles and not to file handles is also inconvenient. So I propose adding a SecurityPlugin facility to control handle access, which would be granted by default, and to add primitives to both the SocketPlugin and FilePlugin to answer the native OS handle when the SecurityPlugin grants permission. I also propose adding a compilation flag to the Windows VM to allow compiling out Andreas' handle management, which consists merely of maintaining a table of the file handles (not the socket handles) that have been created by the VM. It strikes me that a much better solution is merely to encrypt the handle via xoring with a value created at random. I don't see how Andreas' solution adds value, especially since it is not implemented on other platforms, and merely adds overhead. Thoughts? Objections? _,,,^..^,,,_ best, Eliot

3 2

Raffle Results of "Live Programming in Smalltalk development environments survey + raffle"
by Juraj Kubelka Aug. 16, 2017

Aug. 16, 2017

Dear Smalltalkers, thank you again for participating in our survey. We are currently analyzing the results. Here, we would like to announce winners of the survey raffleâ¦ and winners are: - Craig Latta, and - Gabriel Omar Cotelli Congratulations! :-) The raffle draw was recorded and is available at: https://youtu.be/cRfPAAeF-xw <https://youtu.be/cRfPAAeF-xw> We will contact the winners in a private email in order to deliver the books to them. Regards, Juraj Kubelka, Romain Robbes, and Alexandre Bergel

1 0

[CfP Deadline Extension] Workshop on Meta-Programming Techniques and Reflection, Deadline August 20
by Stefan Marr Aug. 16, 2017

Aug. 16, 2017

Call for Papers: Metaâ17 ======================== Workshop on Meta-Programming Techniques and Reflection Co-located with SPLASH 2017 October 22, 2017, Vancouver, Canada Twitter @MetaAtSPLASH http://2017.splashcon.org/track/meta-2017 The heterogeneity of mobile computing, cloud applications, multicore architectures, and other systems leads to increasing complexity of software and requires new approaches to programming languages and software engineering tools. To manage the complexity, we require generic solutions that can be adapted to specific application domains or use cases, making metaprogramming an important topic of research once more. However, the challenges with metaprogramming are still manifold. They start with fundamental issues such as typing of reflective programs, continue with practical concerns such as performance and tooling, and reach into the empirical field to understand how metaprogramming is used and how it affects software maintainability. Thus, while industry accepted metaprogramming on a wide scale with Ruby, Scala, JavaScript and others, academia still needs to answer a wide range of questions to bring it to the same level of convenience, tooling, and programming styles to cope with the increasing complexity of software systems. This workshop aims to explore meta-level technologies that help tackling the heterogeneity, scalability and openness requirements of emerging computations platforms. ### Topics of Interest The workshop is a venue for all approaches that embrace metaprogramming: - from static to dynamic techniques - reflection, meta-level architectures, staging, open language runtimes applications to middleware, frameworks, and DSLs - optimization techniques to minimize runtime overhead - contract systems, or typing of reflective programs reflection and metaobject protocols to enable tooling - case studies and evaluation of such techniques, e.g., to build applications, language extensions, or tools - empirical evaluation of metaprogramming solutions - security in reflective systems and capability-based designs - meta-level architectures and reflective middleware for modern runtime platforms (e.g. IoT, cyber-physical systems, mobile/cloud/grid computing, etc) - surveys, conceptualization, and taxonomization of existing approaches In short, we invite contributions to the workshop on a wide range of topics related to design, implementation, and application of reflective APIs and meta-programming techniques, as well as empirical studies and typing for such systems and languages. ### Workshop Format and Submissions This workshop welcomes the presentation of new ideas and emerging problems as well as mature work as part of a mini-conference format. Furthermore, we plan interactive brainstorming and demonstration sessions between the formal presentations to enable an active exchange of ideas. Therefore, we seek the following kinds of publications: â¢ technical paper: max. 8 pages, excluding references â¢ position and work-in-progress paper: 1-4 pages, excluding references â¢ technology demos or a posters: 1-page abstract All papers are to be submitted using the SIGPLAN acmart style. Please use the provided double-column Latex or Word templates. For the submission, please use the submission system at: https://meta17.hotcrp.com/ The workshop technical papers will be published in the ACM DL, if not requested otherwise by the authors. Thus, they will be part of SPLASH workshop proceedings. Demos, posters, position and work-in-progress papers can be submitted on a second, later deadline to discuss the latest results and current work and wonât be included in the ACM DL proceedings. ### Important Dates Abstract Submission: 07 August 2017 Paper Submission: 20 August 2017 Author Notification: 06 September 2017 Position/WIP Paper Deadline: 08 September 2017 Camera Ready Deadline: 18 September 2017 Position/WIP Notification: 21 September 2017 ### Program Committee The program committee consists of the organizers and the following reviewers: Anya Helen Bagge, University of Bergen, Norway Daniele Bonetta, Oracle Labs, Austria Nicolas Cardozo, Universidad de los Andes, Colombia Sebastian Erdweg, TU Delf, The Nederlands Robert Hirschfeld, HPI, Germany Roberto Ierusalimschy, PUC-Rio, Brazil Pablo Inostroza, CWI, The Nederlands Kim Mens, Universite Catholique de Louvain, Belgium Cyrus Omar, Carnegie Mellon University, USA Guillermo Polito, CNRS, France Tiark Rompf, Purdue University, USA Tom Van Cutsem, Nokia Bell Labs, Belgium Takuo Watanabe, Tokyo Institute of Technology, Japan ### Workshop Organizers Shigeru Chiba, University of Tokyo Elisa Gonzalez Boix, Vrije Universiteit Brussel Stefan Marr, Johannes Kepler University Linz ### Contact information For further inquires, do not hesitate to contact the organizers via meta AT soft.vub.ac.be http://2017.splashcon.org/track/meta-2017 -- Stefan Marr Johannes Kepler UniversitÃ¤t Linz http://stefan-marr.de/research/

2 4

Issue 20309 - Startup should run always in a fresh process
by Guillermo Polito Aug. 16, 2017

Aug. 16, 2017

Hi all, I'm proposing a kind-of critical change that I believe is very good for the health of the system: I want that the startup of the system runs in maximum priority and becomes non-interruptable. Right now, when you save your image, the shutdown and startup are run in the same priority than the process that triggered the save (usually the ui or the command line, priority 40). This can cause lots of problems and race conditions: processes with higher priorities can interrupt the shutdown/startup and try to do something while the system is unstable. As a side effect also, when you use extensively the command line, you start stacking startup contexts from old sessions: ... session 3 ctxt 4 <- This guy makes a save and a new session starts session 3 ctxt 3 session 3 ctxt 2 session 3 ctxt 1 session 2 ctxt 4 <- This guy makes a save and a new session starts session 2 ctxt 3 session 2 ctxt 2 session 2 ctxt 1 session 1 ctxt 4 <- This guy makes a save and a new session starts session 1 ctxt 3 session 1 ctxt 2 session 1 ctxt 1 Old contexts are never collected, and the objects they referenced neither. To fix these two problems I propose to do every image save/session start in a new process in maximum priority. That way, other process should not be able to interrupt the startup process. Moreover, every session shutdown/startup should happen in a new clean process, to avoid the session stacking. For normal users, this should have no side effect at all. This change will have a good impact on people working on the debugger and the stack such as fueling-out the stack because they will have a cleaner stack. There is however a side-effect/design point to consider: startup actions should be quick to run. If a startup action requires to run a long-running action such as starting a server or managing a command line action, that should run in a separate process with lower priority (usually userPriority). In other words, the startup action should create a new process managing its action. If you want to review (and I'd be glad) Pull request: https://github.com/pharo-project/pharo/pull/198 Fogbugz issue: https://pharo.fogbugz.com/f/cases/20309 Current validation going on: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… Guille -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

6 18

[Pharo 70 ] build 38 - PR 199 FileReference-size-needs-a-comment
by Stephane Ducasse Aug. 16, 2017

Aug. 16, 2017

https://pharo.fogbugz.com/f/cases/20269/FileReference-size-needs-a-comment https://github.com/pharo-project/pharo/pull/199

1 0

[Pharo 70 ] build 37 - PR 206 File names should not be canonicalised by default
by Stephane Ducasse Aug. 16, 2017

Aug. 16, 2017

https://pharo.fogbugz.com/f/cases/20307/File-names-should-not-be-canonicali… https://github.com/pharo-project/pharo/pull/206

1 0

[Pharo 70 ] build 36 - PR 204 Improve-comment-of-SmallDictionary
by Stephane Ducasse Aug. 15, 2017

Aug. 15, 2017

https://pharo.fogbugz.com/f/cases/20091/Improve-comment-of-SmallDictionary https://github.com/pharo-project/pharo/pull/204

1 0