- Pharo-users - lists.pharo.org

Method comparison
by Davide Varvello June 21, 2024

June 21, 2024

In older Pharo versions it was possible to compare two methods selecting them via UI.Â I couldn't find this opportunity in Pharo10, Â so digging into the source code I found SpDiffPresenter, if you pass to it a couple of selectors it can compare them. Example: SpDiffPresenter new showOptions: true; leftText: (MyObject >> #firstSelector) sourceCode; rightText: (MyObject >> #secondSelector) sourceCode; contextClass: True; openÂ CheersDavide

1 0

This week (25/2024) on the Pharo Issue Tracker
by Marcus Denker June 21, 2024

June 21, 2024

This week we backported some fixes to Pharo12, mostly related to high resolution rendering and Traits # Pharo 12 - Backport change of default value for setting #autoSetCanvasScaleFactor to true #16783 https://github.com/pharo-project/pharo/pull/16783 - Remove (wrong) primitive usage #16781 https://github.com/pharo-project/pharo/pull/16781 - [Backport] Port fixes on traits and metaclasses to Pharo 12 #16776 https://github.com/pharo-project/pharo/pull/16776 - Backport use of FormSet for #withCloseBox and #withPinBox on MenuTitleMorph #16774 https://github.com/pharo-project/pharo/pull/16774 - Backport selective removal of entries in #shrinkTo: on FreeTypeCache #16773 https://github.com/pharo-project/pharo/pull/16773 - [P12][Backport] fix #needRequestorScope of StDebuggerContextInteractionModel so that its bindings can be used when evaluating code in the debugger #784 https://github.com/pharo-spec/NewTools/pull/784 # VM - New harmonize rule #817 https://github.com/pharo-project/pharo-vm/pull/817 - Fixing warnings that are errors in newer versions of clang #813 https://github.com/pharo-project/pharo-vm/pull/813 - Adding an implementation of the aio.c using EPOLL in Linux. #805 https://github.com/pharo-project/pharo-vm/pull/805 - Ignoring EAGAIN in epoll_wait #818 https://github.com/pharo-project/pharo-vm/pull/818 # Features - Update roassal to v1.06f #16770 https://github.com/pharo-project/pharo/pull/16770 - Propose a DarkBlueTheme #16777 https://github.com/pharo-project/pharo/pull/16777 - Make setting pages less dense without comments for each setting #772 https://github.com/pharo-spec/NewTools/pull/772 # Fixes - test file dialogs returns the selected file #778 https://github.com/pharo-spec/NewTools/pull/778 - Revert "Use taskbar icon name for inspector and playground" #779 https://github.com/pharo-spec/NewTools/pull/779 - Fix issue when opening custom scope on calypso #783 https://github.com/pharo-spec/NewTools/pull/783 - Fix Open Playground menu item hanging the image #787 https://github.com/pharo-spec/NewTools/pull/787 - Add back old playground shortcut with deprecation #16788 https://github.com/pharo-project/pharo/pull/16788 - Remove (wrong) primitive usage #16780 https://github.com/pharo-project/pharo/pull/16780 - add missing accessor #1558 https://github.com/pharo-spec/Spec/pull/1558 - adding test to ensure it is possible to recompile code within a bloc with a dead home context twice #723 https://github.com/pharo-spec/NewTools/pull/723 # Refactoring Engine - Migrate Refactoring for Generating Equal and Hash Methods #16786 https://github.com/pharo-project/pharo/pull/16786 # Cleanup - Remove call to deprecated Author #83 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/83 - Remove deprecated classes and methods #758 https://github.com/pharo-spec/NewTools/pull/758 - Removing UIMnagaer dependencies from the debugger infrastructure #16015 https://github.com/pharo-project/pharo/pull/16015 - The debugger now delegate UI decisions to the backend provided by its application #667 https://github.com/pharo-spec/NewTools/pull/667 - Fix deprecated usage of StInspector #16769 https://github.com/pharo-project/pharo/pull/16769 - taskbarIcon moved to SystemWindow #16792 https://github.com/pharo-project/pharo/pull/16792 - Rename RBNode into ASTNode #16596 https://github.com/pharo-project/pharo/pull/16596

1 0

Spec2 - Morph query & move window to another position
by Haroldo Stenger June 18, 2024

June 18, 2024

hi all there , I'm playing around with this example from the nice Spec book, which I try to get right for spec2. That's all right. I modify the example for having two counters, one bound to the class of the Surveys and then one for each survey. That was a good learning experience. Then I added a button to spawn further a Survey which participates of the class-bound count of votes. That's all right too. Then I started to write a method that given a Rectangle, and a number n, gives an array of n Points that are in the enclosed circle of the rectangle, more or less. Waht I want to achieve es that for each added Survey, its Spec2 - Morph window gets positioned in one of these points, but before rendering it, re position all the already existing Spec2 - Morphs Survey windows in the rest of the points of the array (being n the total number of Surveys after adding one). I'm facing two challenges: (a) getting the list of current positions of Spec2 - Morph Surveys already existing. (b) moving a Spec2 - Morph window to another position. I'm pretty stuck trying to make my way for this two goals, so any kind help will be really welcome. Yo can import the files into a Pharo12 image with the File manager, then Changelist Browser and selecting all the lines and "file in". thanks in advance ! Haroldo

2 3

Pharo VM v10.2.1
by tesonep＠gmail.com June 14, 2024

June 14, 2024

Hi, there is a new release of the VM ## v10.2.1 * Adding the missing tty.c file in the packaging. by @tesonep in https://github.com/pharo-project/pharo-vm/pull/771 * Do not allow comparing objects of different types by @guillep in https://github.com/pharo-project/pharo-vm/pull/772 * Prepare release 10.2.1 by @guillep in https://github.com/pharo-project/pharo-vm/pull/773 * Constant conversion warning by @guillep in https://github.com/pharo-project/pharo-vm/pull/777 * Fix tautological-pointer-compare warnings by @guillep in https://github.com/pharo-project/pharo-vm/pull/775 * Removed Cogit>>#voidNSSendCache: by @jordanmontt in https://github.com/pharo-project/pharo-vm/pull/776 * Re-enable incompatible-function-pointer-types warning by @guillep in https://github.com/pharo-project/pharo-vm/pull/778 * Removed unused functions from the C written by hand by @jordanmontt in https://github.com/pharo-project/pharo-vm/pull/780 * Fix function pointer comparison warning by @guillep in https://github.com/pharo-project/pharo-vm/pull/783 * Fix -return-type warnings by @doste in https://github.com/pharo-project/pharo-vm/pull/781 * Fix shift-negative-value warning and reenable warning by @guillep in https://github.com/pharo-project/pharo-vm/pull/785 * Remove warnings c compiler by @PalumboN in https://github.com/pharo-project/pharo-vm/pull/789 * Remove StackInterpreter interruptPending instance variable by @jordanmontt in https://github.com/pharo-project/pharo-vm/pull/793 * Do not use asserta: in a statement by @guillep in https://github.com/pharo-project/pharo-vm/pull/788 * Bump to MacOS 11 and above by @guillep in https://github.com/pharo-project/pharo-vm/pull/792 * Moving pharo.signatures files for OSX Bundle to Resources folder by @tesonep in https://github.com/pharo-project/pharo-vm/pull/770 * Do not retain any selectors in CogAbstractInstruction by @RenaudFondeur in https://github.com/pharo-project/pharo-vm/pull/798 * remove warning because of type and unsigned shift issues by @RenaudFondeur in https://github.com/pharo-project/pharo-vm/pull/800 * add tests for type harmonization by @RenaudFondeur in https://github.com/pharo-project/pharo-vm/pull/807 * Primitive format by @doste in https://github.com/pharo-project/pharo-vm/pull/802 * Adding an implementation of the aio.c using EPOLL in Linux. by @tesonep in https://github.com/pharo-project/pharo-vm/pull/805 * Fixing warnings that are errors in newer versions of clang by @tesonep in https://github.com/pharo-project/pharo-vm/pull/813 ## New Contributors * @RenaudFondeur made their first contribution in https://github.com/pharo-project/pharo-vm/pull/798 **Full Changelog**: https://github.com/pharo-project/pharo-vm/compare/v10.2.0...v10.2.1 More Information: https://github.com/pharo-project/pharo-vm/releases/tag/v10.2.1 -- Pablo Tesone. tesonep(a)gmail.com

1 0

This week (24/2024) on the Pharo Issue Tracker
by Marcus Denker June 14, 2024

June 14, 2024

# Pharo 12 - Fix Issue: Backport Pharo12: Wrong source for CompiledBlocks due to incorrect bytecode to AST nodes mapping #16756 https://github.com/pharo-project/pharo/pull/16756 # Improvemetns - Adds a simple MoveTo taskbar menu item #16544 https://github.com/pharo-project/pharo/pull/16544 - replace JPEGReadWriter by PluginBasedJPEGReadWriter and deprecate theâ¦ #16535 https://github.com/pharo-project/pharo/pull/16535 - return the result of ok action and simplify file selection #776 https://github.com/pharo-spec/NewTools/pull/776 - withWindowDo: should return the result of the block #1555 https://github.com/pharo-spec/Spec/pull/1555 - Update after selection in Color Picker #766 https://github.com/pharo-spec/NewTools/pull/766 - New dialog to select multiple items using checkboxes #1548 https://github.com/pharo-spec/Spec/pull/1548 # Fixes - fix preLoading.st #1557 https://github.com/pharo-spec/Spec/pull/1557 - fixing recompilation of bloc in the debugger with dead home context whose method has already been recompiled in the debugger before #16319 https://github.com/pharo-project/pharo/pull/16319 - Fix comparison of two Deprecation objects #16735 https://github.com/pharo-project/pharo/pull/16735 - Updated text to new shortcut #764 https://github.com/pharo-spec/NewTools/pull/764 # Tools - Added new subclass with unified view based on SpDiffPresenter #1452 https://github.com/pharo-spec/Spec/pull/1452 - Add StProtocolNameChooserPresenter #759 https://github.com/pharo-spec/NewTools/pull/759 - Spotter split case #773 https://github.com/pharo-spec/NewTools/pull/773 - Use new StProtocolNameChooserPresenter to replace morphic tool #16690 https://github.com/pharo-project/pharo/pull/16690 - Icon for debugger in the toolbar #16661 https://github.com/pharo-project/pharo/pull/16661 - ProfilerUI: Added a warning when trying to compile and the variables are not declared #741 https://github.com/pharo-spec/NewTools/pull/741 - Update playground shortcut #738 https://github.com/pharo-spec/NewTools/pull/738 # Cleanups - Remove deprecated code #1545 https://github.com/pharo-spec/Spec/pull/1545 - Remove references to SystemAnnouncer singleton #742 https://github.com/pharo-spec/NewTools/pull/742 - Move some debugger related code of Process to debugger packages #15799 https://github.com/pharo-project/pharo/pull/15799 - Moved pragma declaration to top of methods #16728 https://github.com/pharo-project/pharo/pull/16728 - Categorization rules tests #16767 https://github.com/pharo-project/pharo/pull/16767

1 0

This week (23/2024) on the Pharo Issue Tracker
by Marcus Denker June 7, 2024

June 7, 2024

# Pharo 12 - Fix/Update Iceberg #16752 https://github.com/pharo-project/pharo/pull/16752 - 16733-Backport-Pharo12-DebugPoint-on-class-side-method-16682 #16734 https://github.com/pharo-project/pharo/pull/16734 - fix bad label before first progress event. #1551 https://github.com/pharo-spec/Spec/pull/1551 - Updating LibGit2 #1827 https://github.com/pharo-vcs/iceberg/pull/1827 # Features - Add newTenured allocation methods #16729 https://github.com/pharo-project/pharo/pull/16729 - Fix ZnBufferedWriteStream does not support #reset #16727 https://github.com/pharo-project/pharo/pull/16727 - Primitive format #802 https://github.com/pharo-project/pharo-vm/pull/802 # Fixes - fix bad label before first progress event. #1552 https://github.com/pharo-spec/Spec/pull/1552 - add missing code from P12 #763 https://github.com/pharo-spec/NewTools/pull/763 - 16495-Wrong-source-for-CompiledBlocks-due-to-incorrect-bytecode-to-AST-nodes-mapping #16664 https://github.com/pharo-project/pharo/pull/16664 - Calypso cmd-v method versions shortcut #16742 https://github.com/pharo-project/pharo/pull/16742 - Fix Random seed with float value #16738 https://github.com/pharo-project/pharo/pull/16738 # Refactoring Engine - Add subclass driver #16353 https://github.com/pharo-project/pharo/pull/16353 - Refactor: inline method cleaning #16745 https://github.com/pharo-project/pharo/pull/16745 # Rules - Add setting rules feature #16750 https://github.com/pharo-project/pharo/pull/16750 - Move rules matadatas to class side #16705 https://github.com/pharo-project/pharo/pull/16705 # ClassBuilder / Traits - Fix multiple bugs in metaclass management of ShiftClassBuilder #16722 https://github.com/pharo-project/pharo/pull/16722 - Fix bug causing classes to lose their traits. #16739 https://github.com/pharo-project/pharo/pull/16739 - Use #update:to: instead of #make: and #fillFor: #16746 https://github.com/pharo-project/pharo/pull/16746 # Cleanups - Remove deprecated aliases of P12 #16659 https://github.com/pharo-project/pharo/pull/16659

1 0

Can the rewrite tool replace a single statement with multiple statements?
by Tim Mackinnon June 5, 2024

June 5, 2024

I've never really learned the rewrite tool but while waiting for changes to propagate through P12, I thought maybe I could use it to safely patch changes until there are official updates (and it was a good chance to get more familiar with it). I thought there was more documentation available for how it works (interested in any old articles - but the online help in P12 is ok - although it doesn't display in markdown - in fact give there is markdown support now - I am a bit confused what should appear more readable these days - and how to fix/contribute changes to help). This aside - I wanted to patch the SystemWindow>>taskbarButtonMenu: (and add my fix to move tabs to any position). I started writing the following search expression - the find the last call to #addToggle:... method call that has a literal referencing #canBeMovedRight - as I want to add my new menu item after it. e.g. moveSubmenu `@addToggle: `{ :node | node isLiteralNode and: [ node value = #canBeMovedToRight] } but I'm not sure my {} filter block is ever called, as the above matches both addToggle:... calls, and not the one I'm after? I don't understand this - any have ideas on the proper syntax for generic matching? Anyway - I decided that in my case there is only one - so I can match it explicitly and so I search on the full call: and I entered this: moveSubmenu addToggle: 'Move right' translated target: self selector: #taskbarMoveRight getStateSelector: nil enablementSelector: #canBeMovedToRight. Which matches exactly - then I want to replace the single statement with 2 statements e.g. moveSubmenu addToggle: 'Move right' translated target: self selector: #taskbarMoveRight getStateSelector: nil enablementSelector: #canBeMovedToRight. moveSubmenu addToggle: 'Move to' translated target: self selector: #taskbarMoveTo getStateSelector: nil. However this gives an error in the rewrite tool (actually it results in a zero change, that then gives an error for EpMonitor). But my question is - why can't you rewrite a single statement to multiple ones? I have noticed that in this case I can cascade the message send - and this then rewrites properly - so it looks like it wants to replace a single node with a single node. If I couldn't cascade - It seems I would have to rewrite with something like: [ "put multiple expressions here" ] value. This seems an odd choice - but am I missing something obvious? Do you have to do what I'm proposing in 2 steps - rewrite to a block (or some equivalent) and then a 2nd rewrite to simplify the expression (like a refactor step) - so its more provably correct? I'm just curious on this - as it seemed time to learn this properly? Tim

3 6

Recent Pharo's seem to lose first keystroke when you swap to them to paste?
by Tim Mackinnon June 1, 2024

June 1, 2024

For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. Tim

7 10

12 Month engineer position at Toulouse in Pharo
by stephane ducasse June 1, 2024

June 1, 2024

Hi people Can you distribute this job position around you? Yannick Chevalier has a position to develop a tool to detect abnomalies DeÌveloppement de lâoutil iCANt pour la deÌtection dâanomalies <mailto:yannick.chevalier@gmail.com> Who: yannick.chevalier(a)gmail.com <mailto:yannick.chevalier@gmail.com> Where: Toulouse Salary: 45 K Euros a more experienced dev could be hired for a shorter period and get a better salary. S. StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

1 0

2nd CfP: SLE 2024 - 17th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis May 31, 2024

May 31, 2024

17th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2024) October 20-21, 2024 Pasadena, California, United States --------------------------- Important Dates --------------------------- * Abstract Submissions: Fri 14 Jun, 2024 * Paper Submissions: Mon 24 Jun, 2024 * Authors Response Period: Mon 12 Aug - Sat 17 Aug, 2024 * Authors Notification: Fri 30 Aug 2024 * Conference: Sun 20 October - Mon 21 October 2024 (co-located with SPLASH) All dates are Anywhere on Earth (https://en.wikipedia.org/wiki/Anywhere_on_Earth) ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 17th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2024), held in conjunction with SPLASH 2024. The conference will be hosted in Pasadena, California, United States on October 20-21, 2024. https://www.sleconf.org/2024/ https://2024.splashcon.org/track/sle-2024 Follow us on X: https://x.com/sleconf --------------------------- Topics of Interest --------------------------- SLE covers software language engineering in general, rather than engineering a specific software language. Topics of interest include, but are not limited to: * Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral/executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches * Validation of Software Language Tools and Implementations - Verification and formal methods for language tools and implementations - Testing techniques for language tools and implementations - Simulation techniques for language tools and implementations * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms * Domain-Specific Approaches for Any Aspects of SLE (analysis, design, implementation, validation, maintenance) * Empirical Studies and Experience Reports of Tools - User studies evaluating usability - Performance benchmarks - Industrial applications * Synergies between Language Engineering and Emerging/Promising Research Areas - AI and ML language engineering (e.g., ML compiler testing, code classification) - Quantum language engineering (e.g., language design for quantum machines) - Language engineering for cyber-physical systems, IoT, digital twins, etc. - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) - Etc. --------------------------- Types of Submissions --------------------------- SLE accepts the following types of papers: Research papers: These are âtraditionalâ papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. New ideas/vision papers: These papers may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas/vision papers must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. SLE Body of Knowledge: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools, and methods developed by the SLE community. These papers can focus on, but are not limited to, methods, techniques, best practices, and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. Tool papers: These papers focus on the tooling aspects often forgotten or neglected in research papers. A good tool paper focuses on practical insights that will likely be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. They may optionally include an appendix with a demo outline/screenshots and/or a short video/screencast illustrating the tool. **Workshops**: Workshops will be organized by SPLASH. Please inform us and contact the SPLASH organizers if you would like to organize a workshop of interest to the SLE audience. Information on how to submit workshops can be found on the SPLASH 2024 Website. --------------------------- Submission --------------------------- SLE 2024 has a single submission round for papers, including a rebuttal phase, where all authors of research papers will have the possibility of responding to the reviews on their submissions. Authors of accepted research papers will be invited to submit artifacts. --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format âacmartâ (https://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template, and that the document class definition is `\documentclass[sigplan,anonymous,review]{acmart}`. Do not make any changes to this format! Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes in figures and tables are legible. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. Accordingly, SLE will follow the double-blind process. Author names and institutions must be omitted from submitted papers, and references to the authorsâ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. All submissions must be in PDF format. The submission website is: https://sle24.hotcrp.com --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy (https://www.sigplan.org/Resources/Policies/Republication/) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism (https://www.acm.org/publications/policies/plagiarism-overview) Submissions that violate these policies will be desk-rejected. --------------------------- Policy on Human Participant and Subject Research --------------------------- Authors conducting research involving human participants and subjects must ensure that their research complies with their local governing laws and regulations and the ACMâs general principles, as stated in the ACMâs Publications Policy on Research Involving Human Participants and Subjects (https://www.acm.org/publications/policies/research-involving-human-particip…) If submissions are found to be violating this policy, they will be rejected. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning soundness, relevance, novelty, presentation, and replicability. New ideas/vision papers will be evaluated primarily concerning soundness, relevance, novelty, and presentation. SLEBoK papers will be reviewed on their soundness, relevance, originality, and presentation. Tool papers will be evaluated concerning relevance, presentation, and replicability. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review at the discretion of the PC chairs. For research papers, authors will get a chance to respond to the reviews before a final decision is made. --------------------------- Artifact Evaluation --------------------------- SLE will use an evaluation process to assess the quality of artifacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artifacts. For more information, please see the Artifact Evaluation (https://2024.splashcon.org/track/sle-2024#Artifact-Evaluation) page. --------------------------- Awards --------------------------- Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. Distinguished artifact: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. **AUTHORS TAKE NOTE**: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- SLE and Doctoral Students --------------------------- SLE encourages students to submit to the SPLASH doctoral symposium. Authors of accepted doctoral symposium papers on SLE topics will also have the chance to present their work to the SLE audience. --------------------------- Organisation --------------------------- Chairs: * General chair: Ralf LÃ¤mmel, UniversitÃ¤t Koblenz, Germany * PC co-chair: Peter Mosses, Swansea University and Delft University of Technology, Netherlands * PC co-chair: Juliana Alves Pereira, PontifÃcia Universidade CatÃ³lica do Rio de Janeiro, Brazil * Artifact Evaluation co-chair: Johannes HÃ¤rtel, Software Languages Lab, Vrije Universiteit Brussel * Artifact Evaluation co-chair: Sergio Queiroz de Medeiros, Universidade Federal do Rio Grande do Norte * Publicity chair: Andrei Chis, feenk gmbh, Switzerland Program committee * Andrzej WÄsowski, IT University of Copenhagen * Anthony Anjorin, ZÃ¼hlke Engineering GmbH * Benoit Combemale, University of Rennes, Inria, CNRS, IRISA * Bernd Fischer, Stellenbosch University * Di Wang, Peking University * Dimitris Kolovos, University of York * Elias Castegren, Uppsala University * Elizabeth Scott, Royal Holloway University of London * Esther Guerra, Universidad AutÃ³noma de Madrid * Faezeh Khorram, Huawei Technologies * Fernando Magno QuintÃ£o Pereira, Federal University of Minas Gerais * Prof. Fiona Polack, University of Hull * GÃ¶rel Hedin, Lund University * Guido Salvaneschi, University of St. Gallen * JoÃ£o Saraiva, HASLab/INESC TEC, University of Minho * Johannes HÃ¤rtel, Software Languages Lab, Vrije Universiteit Brussel * Judith Michael, RWTH Aachen University * Manuel Wimmer, JKU Linz * Marc Feeley, UniversitÃ© de MontrÃ©al * Michel Steuwer, Technische UniversitÃ¤t Berlin * Paddy Krishnan, Oracle Labs * Ragnar Mogk, Technische UniversitÃ¤t Darmstadt * Riemer van Rozen, CWI * Roberto Ierusalimschy, PUC-Rio * Sergio Queiroz de Medeiros, Universidade Federal do Rio Grande do Norte * Shigeru Chiba, The University of Tokyo * Stefan Marr, University of Kent * Stephen Chong, Harvard University * TamÃ¡s SzabÃ³, GitHub Next * Thomas Degueule, CNRS * Thomas KÃ¼hn, Martin-Luther-University Halle-Wittenberg * L. Thomas van Binsbergen, University of Amsterdam * Tijs van der Storm, CWI & University of Groningen * Walter Cazzola, UniversitÃ degli Studi di Milano --------------------------- Contact --------------------------- For additional information, clarification, or answers to questions, please get in touch with the program co-chairs (P.D.Mosses at tudelft.nl and Juliana at inf.puc-rio.br).

1 0