- Pharo-users - lists.pharo.org

Wow - Chat GPT understands Smalltalk
by Tim Mackinnon March 27, 2023

March 27, 2023

13 24

This week (12/2023) on the Pharo Issue Tracker. We merged >60 PRs
by Marcus Denker March 24, 2023

March 24, 2023

We merged >60 PRs Of those just 16 for Pharo11, the rest are major cleanups/fixes/speedups in Pharo12. Pharo11 ======= - Disable ReCompactSourceCodeRule for p11 #13075 https://github.com/pharo-project/pharo/pull/13075 - Setting image version in the header of the image file #12954 https://github.com/pharo-project/pharo/pull/12954 - Sync zinc #12824 https://github.com/pharo-project/pharo/pull/12824 Bugs ==== - 12948-Broken-ast-method-on-compiled-block #13094 https://github.com/pharo-project/pharo/pull/13094 - Improving debug session to be able customize debug contexts model #13112 https://github.com/pharo-project/pharo/pull/13112 - add includes: to FinalizationRegistry. #13110 https://github.com/pharo-project/pharo/pull/13110 - fixes case sensitive string literal search (use Ctrl+Shift+U shortcut) #1310 https://github.com/pharo-project/pharo/pull/13103 - add shortcuts to string literal search, fix case insensitive search #1362 https://github.com/pharo-spec/Spec/pull/1362 - fix duplicated repos in Iceberg #13074 https://github.com/pharo-project/pharo/pull/13074 - Patch PNGReadWriter to allow and ignore excess chunks after IEND #13049 https://github.com/pharo-project/pharo/pull/13049 - 13051 improve the memory allocation of sequenceable collection runningof #13052 https://github.com/pharo-project/pharo/pull/13052 - Ensuring that Calypso catches any NotFound errors that could appear when a breakpoint on a test under debug doesn' exist anymore #13021 https://github.com/pharo-project/pharo/pull/13021 - Refactoring debugger extension system to update extensions in all debuggers dynamically, when an extension is (un)activated #481 https://github.com/pharo-spec/NewTools/pull/481 - Fix two deprecated #asOrderedCollection sends #490 https://github.com/pharo-spec/NewTools/pull/490 - skip testDoEvaluateDeclareGlobal for now #492 https://github.com/pharo-spec/NewTools/pull/492 - skip another testDoEvaluateDeclareGlobal for now #493 https://github.com/pharo-spec/NewTools/pull/493 Pharo 12 ======== Major work continuesâ¦ of note are the speed improvements. SystemOrganizer now uses a dictionary and we enabled primitive 158 for string comparison, just to name two. Speed ===== - Use primitive 158 for string comparison #12878 https://github.com/pharo-project/pharo/pull/12878 - Speed up FreeTypeFont>>widthOf: #13116 https://github.com/pharo-project/pharo/pull/13116 - Speed up in rpackage #13086 https://github.com/pharo-project/pharo/pull/13086 - Use dictionary in SystemOrganizer #13023 https://github.com/pharo-project/pharo/pull/13023 - Some various speedup #13067 https://github.com/pharo-project/pharo/pull/13067 - Do not fire systemClassRecategorizedActionFrom: everytime #13066 https://github.com/pharo-project/pharo/pull/13066 - Speedup RBBrowserEnvironment>>#classesInPackages:do: #13056 https://github.com/pharo-project/pharo/pull/13056 Category/Protocols Cleanup ================= - ClassOrganization>>#classify:under:suppressIfDefault: is always called with the same parameter #13082 https://github.com/pharo-project/pharo/pull/13082 - Rename ClassOrganization #*category* into #*protocolName* #13019 https://github.com/pharo-project/pharo/pull/13019 - Some cleanings of ClassDescription #13046 https://github.com/pharo-project/pharo/pull/13046 - Unify package unregistration #13040 https://github.com/pharo-project/pharo/pull/13040 Compiler ======== - Faulty compiler: new CodeError class #13029 https://github.com/pharo-project/pharo/pull/13029 - Code Snippets: extends tests to check notices #13115 https://github.com/pharo-project/pharo/pull/13115 - RBCodeSnippet format, tidify and better default mechanism #13109 https://github.com/pharo-project/pharo/pull/13109 - Faulty code: position fixes on some ast nodes (and various cleanup) #13098 https://github.com/pharo-project/pharo/pull/13098 - Compiler gets permitFaulty #13084 https://github.com/pharo-project/pharo/pull/13084 - Fauty code: RBParser parse only faulty code #13080 https://github.com/pharo-project/pharo/pull/13080 - Faulty code: keep AST and source information in faulty CompiledMethod #13087 https://github.com/pharo-project/pharo/pull/13087 - RFC: RBNotice to reify error and warning messages on AST nodes #13057 https://github.com/pharo-project/pharo/pull/13057 - Faulty code: strip OCUndeclaredVariableWarning of its reparation duties #13055 https://github.com/pharo-project/pharo/pull/13055 - Make unreachable statements a warning instead of an error #13050 https://github.com/pharo-project/pharo/pull/13050 - Compiler: stop playing notification pingpong #13047 https://github.com/pharo-project/pharo/pull/13047 - Faulty parser - better error position and messages #13044 https://github.com/pharo-project/pharo/pull/13044 - Faulty code - test Monticello #13036 https://github.com/pharo-project/pharo/pull/13036 - Compiler: remove getSourceFromRequestorSelection #13045 https://github.com/pharo-project/pharo/pull/13045 - Faulty parsing: change logic of errorBlock #13042 https://github.com/pharo-project/pharo/pull/13042 - Tests that CI handle properly Syntax Errors during tests #12785 https://github.com/pharo-project/pharo/pull/12785 - Faulty code: CodeError are resumable #13037 https://github.com/pharo-project/pharo/pull/13037 - Improve faulty compilation - unify handling of undeclared variables #13007 https://github.com/pharo-project/pharo/pull/13007 Compiler/Tools ============= - Rubric/Calypso improve menu entries (especially browse) #13095 https://github.com/pharo-project/pharo/pull/13095 - Fix #13107 cannot remove used slot #13118 https://github.com/pharo-project/pharo/pull/13118 - RubSmalltalkEditor-remove-reference-RBParser #13091 https://github.com/pharo-project/pharo/pull/13091 - Calypso editor: stop inserting -> #13073 https://github.com/pharo-project/pharo/pull/13073 Improvements =========== - LongMessageDialogWindow wraps the text #13117 https://github.com/pharo-project/pharo/pull/13117 - Refactoring push up method: introduce driver #12867 https://github.com/pharo-project/pharo/pull/12867 - Fix refacotring bug #13069 https://github.com/pharo-project/pharo/pull/13069 Bootstrap/CI/Housekeeping ========= - Add some timestamps and logs to the bootstrap #13106 https://github.com/pharo-project/pharo/pull/13106 - Remove travis file #13105 https://github.com/pharo-project/pharo/pull/13105 - Make documentation more readable on github #13093 https://github.com/pharo-project/pharo/pull/13093 - Synch with p11 (To get ombu fix crashing the CI) #13081 https://github.com/pharo-project/pharo/pull/13081 - Synch with p11 #13077 https://github.com/pharo-project/pharo/pull/13077 - Log the package been tested on CI. #13038 https://github.com/pharo-project/pharo/pull/13038 Cleanups ======== - Move machineEpsilon to Float. #13078 https://github.com/pharo-project/pharo/pull/13078 - 12996-Remove-ReLiteralArrayContainsSuspiciousTrueFalseOrNilRule #13092 https://github.com/pharo-project/pharo/pull/13092

1 0

UK Smalltalk User Group meeting - Wednesday 29th March
by Giovanni Corriga March 21, 2023

March 21, 2023

This month's online meeting introduces a new format whereby we'll give space to commercial companies to discuss how they make use of Smalltalk and contribute to the Smalltalk community. The first of this series will be Mercap Software ( https://www.mercapsoftware.com/en/ ), represented by Gabriel Cotelli, InÃ©s Sosa, IvÃ¡n Boaretto, MatÃas Fernandez, and Maximiliano Tabacman. During this talk, Mercap will showcase five of their solutions designed for different types of investors. They will shed light on how Mercap benefits from the open-source projects maintained by the Buenos Aires Smalltalk group on GitHub. They will share with you how they use these freely available frameworks to interact with databases, operate on math and time units, create custom CSS, declare interactions on web applications, display complex charts, manage application startup, and streamline the creation of Docker images. Gabriel Cotelli is a CS bachelor, continuous learner & free-thinker. Supporter of libre knowledge, human intelligence augmentation and open source software. Working in Smalltalk at Mercap since 2004. He's an active member of the Smalltalk development community and regular contributor to open source projects in Buenos Aires Smalltalk and Pharo. InÃ©s Sosa writes code in Smalltalk. IvÃ¡n Boaretto is a software developer by day and a computer science student by night. He is very passionate about his craft and is always striving to improve. Now, in his first time at the Smalltalks, he is looking to attract new blood to the wonderful Smalltalk community. MatÃas Fernandez is a software and tech enthusiast, and Smalltalk developer. Maximiliano Tabacman has been a part of Mercap since he started his studies in IT, which now include a PhD in Computer Sciences from the Facultad de Ciencias Exactas y Naturales (UBA). His main interest is the design of systems that apply nature inspired concepts, such as evolutionary algorithms and neural networks. Smalltalk, with its object-message design, is his natural choice for a development platform. He is also the creator of ERA, a standalone web server application for running table-top roleplaying games, which runs on Windows, Mac and Linux. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/292128721/ ) to receive the meeting details.

1 0

searching for pharo code on disk
by Siemen Baader March 21, 2023

March 21, 2023

Hi, I'm looking for some code I wrote maybe 7 years ago. A web scraper that collected data from a specific web shop. It must be somewhere in my home dir in an image, perhaps Pharo 4.0, or in .mcz files stored by Monticello. What would be a good way to search for it? I tried `grep -r --include \*.changes "server-url.com" ~` (I also asked ChatGPT as per the previous discussion on this list, and it tries its best to teach me about grep and sound very convincing while providing me with arguments that grep can't evaluate :)) with no luck so far. Any ideas? Thanks, Siemen

3 2

This week (11/2023) on the Pharo Issue Tracker
by Marcus Denker March 17, 2023

March 17, 2023

This week Pharo11 was frozen. We will focus now on fixing the last remaining show stopping bugs. All non-fixes are now going to the new Pharo12 branch. We merged nearly 40 Pull requests: Pharo 11 ======== Last Improvements =========== - New finalization #12042 https://github.com/pharo-project/pharo/pull/12042 - Add document browser #12787 https://github.com/pharo-project/pharo/pull/12787 Compiler ======== - better fix for #12858: check isTempVariable #12971 https://github.com/pharo-project/pharo/pull/12971 - Fix infinite loop in faulty literal array parsing #12992 https://github.com/pharo-project/pharo/pull/12992 Syntax Highlight =============== - Add regression test to Shout #12974 https://github.com/pharo-project/pharo/pull/12974 - Fix formating of non methods #12987 https://github.com/pharo-project/pharo/pull/12987 - re-Enable Format Incomplete Variables #12998 https://github.com/pharo-project/pharo/pull/12998 Fixes ===== - 179-When-FluidClass-on-Epicea-Tests-break #12977 https://github.com/pharo-project/pharo/pull/12977 - Polymath needs the largest exponant argument. Pharo implements the constant but didn't provide an accessor #12975 https://github.com/pharo-project/pharo/pull/12975 - Fix bug when updating the package of an extension method #12970 https://github.com/pharo-project/pharo/pull/12970 - fix the default loadLibrary: for linux #12938 https://github.com/pharo-project/pharo/pull/12938 - Escape '|' and '.' characters to prevent regex interpretation #13008 https://github.com/pharo-project/pharo/pull/13008 - 11407-CI-System-variable-environment-on-windows-does-not-use-adequate-encodings #12973 https://github.com/pharo-project/pharo/pull/12973 - "Close" instead of "Cancel" in the button label of the Find & Replaceâ¦ #13013 https://github.com/pharo-project/pharo/pull/13013 - Make sure SharedRandom globalGenerator is reset (i.e. a new one is crâ¦ #13022 https://github.com/pharo-project/pharo/pull/13022 - Improve #12992: Copying strings in editor #13026 https://github.com/pharo-project/pharo/pull/13026 Debugger/Inspector =============== - Fixing debugger adding an instance variable not appears in the debugger vars inspector + fixing args duplication when restarting execution #479 https://github.com/pharo-spec/NewTools/pull/479 - Inspect text and string with code font #468 https://github.com/pharo-spec/NewTools/pull/468 - Fixing fuel out command + making it more user-friendly #447 https://github.com/pharo-spec/NewTools/pull/447 - fixing StHaltOnCall execution condition #488 https://github.com/pharo-spec/NewTools/pull/488 Cleanup ======= - Removing makefile files that are obsolete (cheched with Guille) #13009 https://github.com/pharo-project/pharo/pull/13009 - Update vm parameter 45 description #12587 https://github.com/pharo-project/pharo/pull/12587 Pharo 12 ========= Compiler ======== - Improve faulty compilation - unify handling of undeclared variables #13007 https://github.com/pharo-project/pharo/pull/13007 - Kill syntax error debugger #12910 https://github.com/pharo-project/pharo/pull/12910 - Improve OCUndeclaredVariableWarning>>declareTempAndPaste #12978 https://github.com/pharo-project/pharo/pull/12978 - Improve ClyClassDefinitionEditorToolMorph>>applyChanges #12981 https://github.com/pharo-project/pharo/pull/12981 - [for Pharo12] Improve faulty parsing: small things #12995 https://github.com/pharo-project/pharo/pull/12995 - Improve OCUndeclaredVariableWarning>>openMenuIn #12980 https://github.com/pharo-project/pharo/pull/12980 - Improve ClySystemEnvironment>>defineNewClassFrom #12982 https://github.com/pharo-project/pharo/pull/12982 - add RBCodeSnippetTest>>#testCodeImporter #12933 https://github.com/pharo-project/pharo/pull/12933 - Faulty compiler: new CodeError class #13029 https://github.com/pharo-project/pharo/pull/13029 Improvements ============= - Speedup OrderedDictionary class>>#newFromKeys:andValues: #13011 https://github.com/pharo-project/pharo/pull/13011 Cleanups ======== - Simplify Categorizer #13002 https://github.com/pharo-project/pharo/pull/13002 - Merge categorizer with SystemOrganizer #13017 https://github.com/pharo-project/pharo/pull/13017 Syntax Highlight ================ - Fix style of pragmas #13012 https://github.com/pharo-project/pharo/pull/13012 Build / CI Prepare ============ - Fix Pharo 12 loading #13004 https://github.com/pharo-project/pharo/pull/13004 - Use internal FuelPlatform #13010 https://github.com/pharo-project/pharo/pull/13010 Pharo 10 ======== Backport fix to bugged undo-redo commands after using completion #12905 https://github.com/pharo-project/pharo/pull/12905

1 0

[ANN] Launchpad v4.9.0 [v4.9.0] released!
by Buenos Aires Smalltalk March 17, 2023

March 17, 2023

1 0

[ANN] Buoy v6.3.0 [v6.3.0] released!
by Buenos Aires Smalltalk March 16, 2023

March 16, 2023

1 0

[ANN] Bell v1.0.1 [v1.0.1] released!
by Buenos Aires Smalltalk March 16, 2023

March 16, 2023

1 0

This week (10/2023) on the Pharo Issue Tracker
by Marcus Denker March 13, 2023

March 13, 2023

We merged 32 PRs this week: Bugs ==== - InitializedSlot-check-default #12895 https://github.com/pharo-project/pharo/pull/12895 - correcting computation of sets of protocols to remove and add #12962 https://github.com/pharo-project/pharo/pull/12962 - 12955-TFStringType-is-leaking-when-allocates-the-string-for-calling-a-function #12956 https://github.com/pharo-project/pharo/pull/12956 - Fixing bugged undo-redo commands after using completion #12570 https://github.com/pharo-project/pharo/pull/12570 Improvements =========== - Speed up ClassVar>>#isReferenced #12930 https://github.com/pharo-project/pharo/pull/12930 - Add new attributes to SDL_MouseWheelEvent #12897 https://github.com/pharo-project/pharo/pull/12897 - Synch zinc zodiac #12932 https://github.com/pharo-project/pharo/pull/12932 - Add BaselineOf:>>#pharoVersionsFrom: #12908 https://github.com/pharo-project/pharo/pull/12908 - Ensure #setUp is classified in running #12907 https://github.com/pharo-project/pharo/pull/12907 Compiler ======== - RBCodeSnippets test decompilation #12901 https://github.com/pharo-project/pharo/pull/12901 - no more RBScanner errorBlock #12900 https://github.com/pharo-project/pharo/pull/12900 - Improve faulty AST fromatting by RBSimpleFormatter #12902 https://github.com/pharo-project/pharo/pull/12902 - better fix for #12858: check isTempVariable #12971 https://github.com/pharo-project/pharo/pull/12971 - add RBCodeSnippetTest>>testCompileWithRequestor #12958 https://github.com/pharo-project/pharo/pull/12958 - Improve faulty compiling - small snippets cleanup #12947 https://github.com/pharo-project/pharo/pull/12947 - Improve faulty compiling: test shadowed reserved variables #12960 https://github.com/pharo-project/pharo/pull/12960 - Improve faulty reporting: IconStyler #12934 https://github.com/pharo-project/pharo/pull/12934 - Improve faulty compilation - semantic error #12919 https://github.com/pharo-project/pharo/pull/12919 - Improve faulty parsing. Add semantic snippets #12909 https://github.com/pharo-project/pharo/pull/12909 Syntax Highlighter ================== - Simplify styler #12952 https://github.com/pharo-project/pharo/pull/12952 - Improve styler #12915 https://github.com/pharo-project/pharo/pull/12915 - Add regression test to Shout #12974 https://github.com/pharo-project/pharo/pull/12974 - Loop imbricated styles + remove dead code #12964 https://github.com/pharo-project/pharo/pull/12964 - Remove dead code in SHTextStyler #12949 https://github.com/pharo-project/pharo/pull/12949 - Shout: Manage syntax highlight of dynamic array #12953 https://github.com/pharo-project/pharo/pull/12953 - Shout:â¯Rename some styles #12945 https://github.com/pharo-project/pharo/pull/12945 Tools ===== - new class SycInspectNodeCommand to simply inspect an AST node #12904 https://github.com/pharo-project/pharo/pull/12904 - 12807-Executable-comment-syntax-error-leads-to-CI-crash #12894 https://github.com/pharo-project/pharo/pull/12894 - Fix Calypso browsing unloaded package artifacts from Iceberg #12425 https://github.com/pharo-project/pharo/pull/12425 Cleanups ======== remove method Object asOrderedCollection #12852 https://github.com/pharo-project/pharo/pull/12852 Trivial ======= - Fix categories in PaSimpleMatrixExampleTest #12937 https://github.com/pharo-project/pharo/pull/12937 Pharo10 ======= - backport-issue-12955: TFStringType is leaking when allocates the string for calling a function #12966 https://github.com/pharo-project/pharo/pull/12966

1 0

1st CfP: SLE 2023 - 16th ACM SIGPLAN International Conference on Software Language Engineering
by Andrei Chis March 6, 2023

March 6, 2023

------------------------------------------------------------------------ 16th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2023) October 22-27, 2023 Cascais, Lisbon, Portugal http://www.sleconf.org/2023/ Follow us on Twitter: https://twitter.com/sleconf ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 16th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2023), held in conjunction with SPLASH 2023. The conference will be hosted in Cascais, Lisbon, Portugal on October 22-27, 2023. --------------------------- Topics of Interest --------------------------- SLE covers software language engineering 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 * Software Language Validation - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages * 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 * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering 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 physical systems (e.g., CPS, IoT, digital twins) - 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. In this respect, the SLE conference will accept surveys, essays, open challenges, empirical observations, and case study papers on the SLE topics. These 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 2023 Website. --------------------------- Important Dates --------------------------- All dates are Anywhere on Earth. * 1st round submissions - Abstract submissions: March 31, 2023 - Paper submissions: April 7, 2023 - Notification: May 5, 2023 * 2nd round submissions - Abstract submissions: June 26, 2023 - Paper submissions: June 30, 2023 - Review notification: August 11, 2023 (starting of the rebuttal) - Author response period: August 18, 2023 (end of the rebuttal) - Notification: August 25, 2023 * Artifact submissions: August 30, 2023 * Artifact kick-the-tires Author response: September 15, 2023 * Artifact notification: September 29, 2023 * Conference: October 22-27, 2023 (co-located with SPLASH, precise dates to be announced) --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format "acmart"(http://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template(https://www.acm.org/binaries/content/assets/publications/consolida…, 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. In this line, SLE will follow the double-blind process. Author names and institutions should 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://sle23.hotcrp.com --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy (http://www.sigplan.org/Resources/Policies/Republication) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism (http://www.acm.org/publications/policies/plagiarism_policy) 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 comply 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…) Submissions that violate this policy will be rejected. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by the program committee. Research papers and tool papers will be evaluated concerning novelty, correctness, significance, readability, and alignment with the conference call. New ideas/vision papers will be evaluated primarily concerning novelty, significance, readability, and alignment with the conference call. SLEBoK papers will be reviewed on their significance, readability, topicality and capacity of presenting/evaluating/demonstrating a piece of BoK about SLE. 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. --------------------------- Artifact Evaluation --------------------------- For the seventh year, SLE will use an evaluation process for assessing the quality of the 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 have a look at the Artifact Evaluation (http://www.sleconf.org/2023/ArtifactEvaluation.html) page. --------------------------- Awards --------------------------- - **Distinguished paper**: Award for most notable paper, as determined by the PC chairs based on the recommendations of the programme 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 papers will have the chance to present their work to the SLE audience, too. --------------------------- Organisation --------------------------- Chairs: * General chair: JoÃ£o Saraiva, Universidade do Minho, Portugal * PC co-chair: Thomas Degueule, CNRS/LaBRI, France * PC co-chair: Elizabeth Scott, Royal Holloway University of London, United Kingdom * Publicity chair: Andrei Chis, feenk gmbh, Switzerland --------------------------- Contact --------------------------- For additional information, clarification, or answers, please get in touch with the program co-chairs (E.Scott at rhul.ac.uk and thomas.degueule at labri.fr).

1 0