Juillet 2017 - Gambit-list - mailman.iro.umontreal.ca

2nd CfP: IFL 2017 (29th Symposium on Implementation and Application of Functional Languages)
by publicityifl＠gmail.com 13 Jul '17

13 Jul '17

<div dir="ltr">Hello, Please, find below the second call for papers for IFL 2017. Please forward these to anyone you think may be interested. Apologies for any duplicates you may receive. best regards, Jurriaan Hage Publicity Chair of IFL --- IFL 2017 - CALL FOR PAPERS ========================== 29th SYMPOSIUM ON IMPLEMENTATION AND APPLICATION OF FUNCTIONAL LANGUAGES ======================================================================== University of Bristol, UK In cooperation with ACM SIGPLAN Wednesday 30 August - Friday 1 September, 2017 <a href="http://iflconference.org/" target="_blank">http://iflconference.org/</a> Scope ----- The goal of the IFL symposia is to bring together researchers actively engaged in the implementation and application of functional and function-based programming languages. IFL 2017 will be a venue for researchers to present and discuss new ideas and concepts, work in progress, and publication-ripe results related to the implementation and application of functional languages and function-based programming. Peer-review ----------- Following the IFL tradition, IFL 2017 will use a post-symposium review process to produce the formal proceedings. All participants of IFL 2017 are invited to submit either a draft paper or an extended abstract describing work to be presented at the symposium. At no time may work submitted to IFL be simultaneously submitted to other venues; submissions must adhere to ACM SIGPLAN's republication policy: <a href="http://www.sigplan.org/Resources/Policies/Republication" target="_blank">http://www.sigplan.org/Resources/Policies/Republication</a> The submissions will be screened by the program committee chair to make sure they are within the scope of IFL, and will appear in the draft proceedings distributed at the symposium. Submissions appearing in the draft proceedings are not peer-reviewed publications. Hence, publications that appear only in the draft proceedings are not subject to the ACM SIGPLAN republication policy. After the symposium, authors will be given the opportunity to incorporate the feedback from discussions at the symposium and will be invited to submit a revised full article for the formal review process. From the revised submissions, the program committee will select papers for the formal proceedings considering their correctness, novelty, originality, relevance, significance, and clarity. The formal proceedings will appear in the International Conference Proceedings Series of the ACM Digital Library. Important dates --------------- Mon 31 July 2017 : Submission deadline draft papers Wed 2 August 2017 : Notification of acceptance for presentation Fri 4 August 2017 : Early registration deadline Fri 11 August 2017 : Late registration deadline Mon 21 August 2017 : Submission deadline for pre-symposium proceedings Wed 30 August 2017 - Fri 1 September 2017 : IFL Symposium Mon 4 December 2017 : Submission deadline for post-symposium proceedings Wed 31 January 2018 : Notification of acceptance for post-symposium proceedings Mon 12 March 2018 : Camera-ready version for post-symposium proceedings Submission details ------------------ Prospective authors are encouraged to submit papers or extended abstracts to be published in the draft proceedings and to present them at the symposium. All contributions must be written in English. Papers must use the new ACM two columns conference format, which can be found at: <a href="http://www.acm.org/publications/proceedings-template" target="_blank">http://www.acm.org/publications/proceedings-template</a> For the pre-symposium proceedings we adopt a 'weak' page limit of 12 pages. For the post-symposium proceedings the page limit of 12 pages is firm. Authors submit through EasyChair: <a href="https://easychair.org/conferences/?conf=ifl2017" target="_blank">https://easychair.org/conferences/?conf=ifl2017</a> Topics ------ IFL welcomes submissions describing practical and theoretical work as well as submissions describing applications and tools in the context of functional programming. If you are not sure whether your work is appropriate for IFL 2017, please contact the PC chair at <a href="mailto:nicolas.wu@bristol.ac.uk" target="_blank">nicolas.wu(a)bristol.ac.uk</a>. Topics of interest include, but are not limited to: - language concepts - type systems, type checking, type inferencing - compilation techniques - staged compilation - run-time function specialization - run-time code generation - partial evaluation - (abstract) interpretation - metaprogramming - generic programming - automatic program generation - array processing - concurrent/parallel programming - concurrent/parallel program execution - embedded systems - web applications - (embedded) domain specific languages - security - novel memory management techniques - run-time profiling performance measurements - debugging and tracing - virtual/abstract machine architectures - validation, verification of functional programs - tools and programming techniques - (industrial) applications Peter Landin Prize ------------------ The Peter Landin Prize is awarded to the best paper presented at the symposium every year. The honored article is selected by the program committee based on the submissions received for the formal review process. The prize carries a cash award equivalent to 150 Euros. Programme committee ------------------- Chair: Nicolas Wu, University of Bristol, UK - Kenichi Asai, Ochanomizu University, Japan - Sandrine Blazy, University of Rennes 1, France - Carlos Camarao, Universidade Federal de Minas Gerais, Brazil - Stephen Dolan, University of Cambridge, UK - Jurriaan Hage, Utrecht University, Netherlands - Yukiyoshi Kameyama, University of Tsukuba, Japan - Benjamin Lerner, Brown University, USA - Bas Lijnse, Radboud University, Netherlands - Garrett Morris, University of Kansas, USA - Miguel Pagano, Universidad Nacional de C√≥rdoba, Argentina - Tomas Petricek, Alan Turing Institute, UK - Maciej Pir√≥g, University of Wroclaw, Poland - Exequiel Rivas, Universidad Nacional de Rosario, Argentina - Neil Sculthorpe, Nottingham Trent University, UK - Melinda Toth, Eotvos Lorand University, Hungary - Phil Trinder, Glasgow University, UK - Kanae Tsushima, National Institute of Informatics, Japan - Marcos Viera, Universidad de la Republica, Uruguay - Meng Wang, University of Kent, UK Venue ----- The IFL 2017 will be held in association with the Department of Computer Science, University of Bristol, UK. Bristol is located in South West England, and can be easily reached from Bristol Airport. See the website for more information on the venue.</div>  <a style='display: block; margin: 32px 0 40px 0; padding: 10px; font-size: 1em; text-align: center; border: 0; border-top: 1px solid gray; ' href='https://goo.gl/2ksdRv'>powered by GSM. Free mail merge and email marketing software for Gmail.</a>

1 0

<Programming> 2018: 2nd Call for Papers
by Sylvia Grewe 11 Jul '17

11 Jul '17

------------------------------------------------------------------------------------ <Programming> 2018 : The Art, Science, and Engineering of Programming Mon 9 - Thu 12 April 2018 Nice, France http://2018.programming-conference.org/ In 2017, we started a new conference and journal focused on everything to do with programming, including the experience of programming, called <Programming> for short. The first edition of <Programming> was a great success (seehttp://twitter.com/programmingconffor testimonies). Paper submissions and publications are handled by the journal. Accepted papers must be presented at the conference. ******************************************************** CALL FOR PAPERS ******************************************************** <Programming> 2018 accept scholarly papers including essays that advance the knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. PAPER SUBMISSIONS: August 1 2017 (Research Papers Second Submission Deadline) December 1 2017 (Research Papers Third Submission Deadline) We accept submissions covering several areas of expertise. These areas include, but are not limited to: • General-purpose programming • Distributed systems programming • Parallel and multi-core programming • Graphics and GPU programming • Security programming • User interface programming • Database programming • Visual and live programming • Data mining and machine learning programming • Interpreters, virtual machines and compilers • Modularity and separation of concerns • Model-based development • Metaprogramming and reflection • Testing and debugging • Program verification • Programming education • Programming environments • Social coding ******************************************************** IMPORTANT DATES ******************************************************** Research paper submissions: August 1 2017 (Research Papers Second Submission Deadline) December 1 2017 (Research Papers Third Submission Deadline) Research paper first notification (for second submission deadline): October 1 2017 Research paper final notification (for second submission deadline): November 7 2017 Research paper first notification (for third submission deadline): February 1 2018 Research paper final notification (for third submission deadline): March 7 2018 Workshop Proposals: October 1 2017 All important dates can also be found athttp://programming-journal.org/timeline/ ******************************************************** ORGANIZATION ******************************************************** General Chair: Manuel Serrano, INRIA France Local Organizing Chair: Tamara Rezk, INRIA France Organizing Committee: Stefan Marr (workshops), Johannes Kepler University Linz Jennifer B. Sartor (workshops), Software Languages Lab, Vrije Universiteit Brussel Belgium Philipp Haller (student research competition), KTH Royal Institute of Technology, Sweden Tobias Pape (web technology), HPI - University of Potsdam Sylvia Grewe (publicity), Technische Universität Darmstadt Germany Program Committee: Guido Salvaneschi (program chair), Technische Universität Darmstadt, Germany Davide Ancona, University of Genova, Italy Alberto Bacchelli, Delft University of Technology, Netherlands Shigeru Chiba, University of Tokyo, Japan Yvonne Coady, University of Victoria, Canada Susan Eisenbach, Imperial College London, UK Patrick Eugster, TU Darmstadt, Germany and Purdue University, United States Antonio Filieri, Imperial College London, UK Matthew Flatt, University of Utah, United States Lidia Fuentes, Universidad de Málaga, Spain Richard P. Gabriel, Dream Songs, Inc. & HPI, California Jeremy Gibbons, University of Oxford, UK Yossi Gil, Israel Institute of Technology Elisa Gonzalez Boix, Vrije Universiteit Brussel, Belgium Phlipp Haller, KTH Royal Institute of Technology, Sweden Matthew Hammer, University of Colorado, Boulder, United States Felienne Hermans, Delft University of Technology, Netherlands Robert Hirschfeld, Hasso Plattner Institute (HPI), Germany Roberto Ierusalimschy, Pontifical Catholic University of Rio de Janeiro, Brazil Jun Kato, National Institute of Advanced Industrial Science and Technology, Japan Jörg Kienzle, McGill University, Canada Neelakantan R. Krishnaswami, University of Cambridge, UK Ralf Lämmel, University of Koblenz-Landau, Germany Hidehiko Masuhara, Tokyo Institute of Technology, Japan Mira Mezini, Technische Universität Darmstadt, Germany Emerson Murphy-Hill, North Carolina State University, United States Mario Südholt, IMT Atlantique, Nantes, France Sam Tobin-Hochstadt, Indiana University, United States Eelco Visser, Delft University of Technology, Netherlands Tijs van der Storm, CWI & University of Groningen, Netherlands ******************************************************** <Programming> 2018 is kindly supported by: ACM In-Cooperation SIGPLAN (In-cooperation) SIGSOFT (In-cooperation) INRIA France AOSA ********************************************************

1 0

gsc failure on Windows 10
by mikel evins 10 Jul '17

10 Jul '17

I just installed gambit-v48_8_8-windows-visualc64.exe on a machine that has VisualStudio Community 2017 on it (with C++ for CLI tools installed). I tried a quick gsc -exe hello.scm (on a file with a simple hello world in it), and got an error message like this: d:\Users\mikel\Workshop\hello-scm>gsc -exe hello.scm hello.c hello_.c libgambit.lib(os_base.obj) : error LNK2019: unresolved external symbol __iob_func referenced in function ___display_error libgambit.lib(os_shell.obj) : error LNK2019: unresolved external symbol _environ referenced in function ___getenv_UCS_2 hello.exe : fatal error LNK1120: 2 unresolved externals Did I overlook something obvious in the setup or compilation?

3 4

serializing instances of structures
by Vijay Mathew 07 Jul '17

07 Jul '17

I am running into an error with deserialized structure instances: Gambit v4.8.4 > (define-structure color r g b) > (define red (make-color 255 0 0)) > (color-r red) 255 > (define e (object->u8vector red)) > (define red2 (u8vector->object e)) > (color-r red2) *** ERROR IN (console)(a)6.1 -- (Argument 1) Instance of #<type #2 color> expected (color-r '#<color #3 r: 255 g: 0 b: 0>) How can I reliably decode a struct-object? --Vijay

2 1

Memory events starting to be used for things like GC sync, OS:es making API:s.
by Adam 05 Jul '17

05 Jul '17

Hi, Just from the news, memory events are starting to be used for things like GC thread sync, OS:es making API:s. http://jcdav.is/2015/11/09/More-JVM-Signal-Tricks/ https://medium.com/@MartinCracauer/generational-garbage-collection-write-ba…

1 0

leap seconds
by Faré 02 Jul '17

02 Jul '17

Dear Gambit list, I'm using Gambit on Unix, and I'd like to store some real time data with a date stamp. (current-time) seems appropriate, but I'm not sure I understand the treatment of leap seconds -- particularly leap seconds inserted. Is (current-time) output monotonic (assuming a monotonic system clock), or will the output go back in time during leap seconds? What are proper functions to extract a date from (current-time) ? Is it guaranteed to use the Unix Epoch when running on Linux? -#f

2 2