- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #180: 2996-test-failing-on-CI-GTSpotterExtensionsOnClassTesttestBasic
by ci-pharo-ci-jenkins2＠inria.fr March 25, 2019

March 25, 2019

There is a new Pharo build available! The status of the build #180 was: FAILURE. The Pull Request #3001 was integrated: "2996-test-failing-on-CI-GTSpotterExtensionsOnClassTesttestBasic" Pull request url: https://github.com/pharo-project/pharo/pull/3001 Issue Url: https://github.com/pharo-project/pharo/issues/2996 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 18 March 2019
by estebanlm＠gmail.com March 25, 2019

March 25, 2019

Hello! This is my weekly ChangeLog, from 18 March 2019 to 24 March 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=18/3/2019&to=24/3/2019 ChangeLog ========= 21 March 2019: -------------- * I worked (despite being sick ;) ) on fixing how some announcements are handled in +WindowPresenter+ The problem was: +WidgetBuilt+ and +WindowBuilt+ announcers were called after call an open command. This is usuallu not a problem but: * What happens if you run a modal dialog? No announce will be sent until modal is over. * What happens if I want to modify the presenter 'after' is built but 'before' is shown? So, I moved this announcements to right after the window is built, and I added a new vocabulary +#whenOpenedDo:+ to match the older +#whenClosedDo:+ (btw... I think I will need an event to validate window closing... but that's another 2c) 19 March 2019: -------------- * Fixing UFFI architecture problems * * * I spent some time fixing some problems detected in UFFI. What happeneds is that when the inclusion of different architectures, some older asumptions were not valid anymore: 1) +long ~= void*+ This means passing +0+ as a +NULL+ is no longer valid! And that, of course, crashes some libraries, specially on windows. To fix this: * now passing nil will be mapped to +ExternalAddress null+ instead +0+. Somehow, I do not like to use the nil as NULL, and because of that: * I introduced the "constant" value +NULL+. Yes, now you can put +NULL+ in your call invocations and they will be translated to a NULL in the callout. 2) Not all constant values are equivallent. In UFFI, you can do something like this: ---- self ffiCall: #(void aFunction(42)) ---- means passing a constant value instead an argument. This is very useful in some contexts... But we cannot longer assume this value is same size as required. We need to make explicit the type! So, I modified the parser and now you can have calls like this: ---- self ffiCall: #(void aFunction( (ulong) 42 )) ---- Making the thing usable again :) *BEWARE:* This will only work for "numeric" types. You cannot cast anything as in C! cheers! Esteban

1 0

[Pharo 8.0] Build #179: Update Calypso version 0.16.1
by ci-pharo-ci-jenkins2＠inria.fr March 24, 2019

March 24, 2019

There is a new Pharo build available! The status of the build #179 was: FAILURE. The Pull Request #2997 was integrated: "Update Calypso version 0.16.1" Pull request url: https://github.com/pharo-project/pharo/pull/2997 Issue Url: https://github.com/pharo-project/pharo/issues/updateCalypso0160 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[CfP] DLS 2019 - 15th Dynamic Languages Symposium, co-located with SPLASH 2019
by Nick Papoylias March 23, 2019

March 23, 2019

======================================================================== Call for Papers DLS 2019 - 15th Dynamic Languages Symposium Co-located with SPLASH 2019, October 22, Athens, Greece https://conf.researchr.org/home/dls-2019 Follow us @dynlangsym ======================================================================== Dynamic Languages play a fundamental role in todayâs world of software, from the perspective of research and practice. Languages such as JavaScript, R, and Python are vehicles for cutting edge research as well as building widely used products and computational tools. The 15th Dynamic Languages Symposium (DLS) at SPLASH 2019 is the premier forum for researchers and practitioners to share research and experience on all aspects on dynamic languages. DLS 2019 invites high quality papers reporting original research and experience related to the design, implementation, and applications of dynamic languages. Areas of interest are generally empirical studies, language design, implementation, and runtimes, which includes but is not limited to: - innovative language features - innovative implementation techniques - innovative applications - development environments and tools - experience reports and case studies - domain-oriented programming - late binding, dynamic composition, and run-time adaptation - reflection and meta-programming - software evolution - language symbiosis and multi-paradigm languages - dynamic optimization - interpretation, just-in-time and ahead-of-time compilation - soft/optional/gradual typing - hardware support - educational approaches and perspectives - semantics of dynamic languages - frameworks and languages for the Cloud and the IoT Submission Details ------------------ Submissions must neither be previously published nor under review at other events. DLS 2019 uses a single-blind, two-phase reviewing process. Papers are assumed to be in one of the following categories: Research Papers: describe work that advances the current state of the art Experience Papers: describe insights gained from substantive practical applications that should be of a broad interest Dynamic Pearls: describe a known idea in an appealing way to remind the community and capture a readerâs interest The program committee will evaluate each paper based on its relevance, significance, clarity, and originality. The paper category needs to be indicated during submission, and papers are judged accordingly. Papers are to be submitted electronically at https://dls19.hotcrp.com/ in PDF format. Submissions must be in the ACM SIGPLAN conference acmart format, 10 point font, and should not exceed 12 pages. Please see full details in the instructions for authors available at: https://conf.researchr.org/home/dls-2019#Instructions-for-Authors DLS 2019 will run a two-phase reviewing process to help authors make their final papers the best that they can be. Accepted papers will be published in the ACM Digital Library and will be freely available for one month, starting two weeks before the event. Important Deadlines ------------------- Abstract Submission: May 29, 2019 Paper Submission: June 5, 2019 First Phase Notification: July 3, 2019 Final Notifications: August 14, 2019 Camera Ready: August 28, 2019 All deadlines are 23:59 AoE (UTC-12h). 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 your conference. The official publication date affects the deadline for any patent filings related to published work. Program Committee ----------------- Alexandre Bergel, University of Chile Carl Friedrich Bolz-Tereick, Heinrich-Heine-UniversitÃ¤t DÃ¼sseldorf Chris Seaton, Oracle Labs David Chisnall, Microsoft Research Elisa Gonzalez Boix, Vrije Universiteit Brussel Gregor Richards, University of Waterloo Guido Chari, Czech Technical University Hannes Payer, Google James Noble, Victoria University of Wellington Jeremy Singer, University of Glasgow Joe Gibbs Politz, University of California San Diego Juan Fumero, The University of Manchester Julien Ponge, Red Hat Mandana Vaziri, IBM Research Manuel Serrano, Inria Marc Feeley, UniversitÃ© de MontrÃ©al Mark Marron, Microsoft Research Na Meng, Virginia Tech Nick Papoulias, UniversitÃ© Grenoble Alpes Richard Roberts, Victoria University of Wellington Sam Tobin-Hochstadt, Indiana University Sarah Mount, Aston University SÃ©bastien Doeraene, Ãcole polytechnique fÃ©dÃ©rale de Lausanne William Cook, University of Texas at Austin Program Chair ------------- Stefan Marr, University of Kent, United Kingdom

1 0

[Pharo 8.0] Build #178: 2993-update-slot-comments
by ci-pharo-ci-jenkins2＠inria.fr March 23, 2019

March 23, 2019

There is a new Pharo build available! The status of the build #178 was: SUCCESS. The Pull Request #2994 was integrated: "2993-update-slot-comments" Pull request url: https://github.com/pharo-project/pharo/pull/2994 Issue Url: https://github.com/pharo-project/pharo/issues/pharo8 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #177: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr March 23, 2019

March 23, 2019

There is a new Pharo build available! The status of the build #177 was: SUCCESS. Could not extract further issue information from commit message: improve stale comment Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #176: 2864-CompiledMethodcommentsIn-should-be-enhanced
by ci-pharo-ci-jenkins2＠inria.fr March 22, 2019

March 22, 2019

There is a new Pharo build available! The status of the build #176 was: SUCCESS. The Pull Request #2950 was integrated: "2864-CompiledMethodcommentsIn-should-be-enhanced" Pull request url: https://github.com/pharo-project/pharo/pull/2950 Issue Url: https://github.com/pharo-project/pharo/issues/2864 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #175: 2987-provide-standard-class-comment-for-tests
by ci-pharo-ci-jenkins2＠inria.fr March 22, 2019

March 22, 2019

There is a new Pharo build available! The status of the build #175 was: SUCCESS. The Pull Request #2988 was integrated: "2987-provide-standard-class-comment-for-tests" Pull request url: https://github.com/pharo-project/pharo/pull/2988 Issue Url: https://github.com/pharo-project/pharo/issues/2987 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #174: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr March 22, 2019

March 22, 2019

There is a new Pharo build available! The status of the build #174 was: SUCCESS. Could not extract further issue information from commit message: Update config.yml fixes #2983. The messages need to be improved. The idea is to point to the documents and tutorials (e.g. how to make a Pull request, what needs to happen to get a PR integrated...) Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #173: FAILURE
by ci-pharo-ci-jenkins2＠inria.fr March 22, 2019

March 22, 2019

There is a new Pharo build available! The status of the build #173 was: FAILURE. Could not extract further issue information from commit message: Update config.yml fixes #2982 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0