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

[TFPIE 2015] 2nd call for papers
by Peter Achten 05 Mar '15

05 Mar '15

Trends in Functional Programming in Education (TFPIE 2015) 2nd Call for papers https://wiki.science.ru.nl/tfpie/TFPIE2015 The 4th International Workshop on Trends in Functional Programming in Education, TFPIE 2015, will be held on June 2, 2015 in Sophia-Antipolis in France. It is co-located with the Symposium on Trends in Functional Programming (TFP 2015) which takes place from June 3 - 5. *** Goal *** The goal of TFPIE is to gather researchers, teachers and professionals that use, or are interested in the use of, functional programming in education. TFPIE aims to be a venue where novel ideas, classroom-tested ideas and work-in-progress on the use of functional programming in education are discussed. The one-day workshop will foster a spirit of open discussion by having a review process for publication after the workshop. The program chair of TFPIE 2015 will screen submissions to ensure that all presentations are within scope and are of interest to participants. Potential presenters are invited to submit an extended abstract (4-6 pages) or a draft paper (up to 16 pages) in EPTCS style. The authors of accepted presentations will have their preprints and their slides made available on the workshop's website/wiki. Visitors to the TFPIE 2015 website/wiki will be able to add comments. This includes presenters who may respond to comments and questions as well as provide pointers to improvements and follow-up work. After the workshop, presenters will be invited to submit (a revised version of) their article for review. The PC will select the best articles for publication in the journal Electronic Proceedings in Theoretical Computer Science (EPTCS). Articles rejected for presentation and extended abstracts will not be formally reviewed by the PC. TFPIE workshops have previously been held in St Andrews, Scotland (2012), Provo Utah, USA (2013), and Soesterberg, The Netherlands (2014). *** Program Committee *** Peter Achten, Radboud University Nijmegen, The Netherlands Edwin Brady, University of St Andrews, UK Johan Jeuring, Utrecht University and Open University, The Netherlands (Chair) Shriram Krishnamurthi, Brown University, US Rita Loogen, Philipps-Universität Marburg, Germany Marco Morazan, Seton Hall University, US Norman Ramsey, Tufts University, US *** Submission Guidelines *** TFPIE 2015 welcomes submissions describing techniques used in the classroom, tools used in and/or developed for the classroom and any creative use of functional programming (FP) to aid education in or outside Computer Science. Topics of interest include, but are not limited to: - FP and beginning CS students - FP and Computational Thinking - FP and Artificial Intelligence - FP in Robotics - FP and Music - Advanced FP for undergraduates - Tools supporting learning FP - FP in graduate education - Engaging students in research using FP - FP in Programming Languages - FP in the high school curriculum - FP as a stepping stone to other CS topics - FP and Philosophy *** Best Lectures *** In addition to papers, we request “best lecture” presentations. What is your best lecture topic in an FP related course? Do you have a fun way to present FP concepts to novices or perhaps an especially interesting presentation of a difficult topic? In either case, please consider sharing it. Best lecture topics will be selected for presentation based on a short abstract describing the lecture and its interest to TFPIE attendees. *** Submission *** Papers and abstracts can be submitted via easychair at the following link: https://easychair.org/conferences/?conf=tfpie2015 It is expected at at least one author for each submitted paper will attend the workshop. *** Important Dates *** April 7, 2015: Early Registration for TFP closes April 27, 2015: Submission deadline for draft TFPIE papers and abstracts May 3 2015: Notification of acceptance for presentation ?? (Probably May 22 2015): Registration for TFPIE closes - as does late registration for TFP June 2, 2015: Presentations in Sophia-Antipolis, France July 7, 2015: Full papers for EPTCS proceedings due. September 1, 2015: Notification of acceptance for proceedings September 22, 2015: Camera ready copy due for EPTCS Submission of an abstract implies no obligation to submit a full version; abstracts with no corresponding full versions by the full paper deadline will be considered as withdrawn.

1 0

Runtime problem with Gambit 4.7.4
by Emmanuel Medernach 05 Mar '15

05 Mar '15

Hello, I have problem running a bunch of code compiled with gambit scheme version 4.7.4 which runned fine with version 4.6.9. This problem tracked down to macros, here is a minimal file: $ cat list.scm (define-syntax dummy (syntax-rules () ((dummy a b ...) (time (begin a b ...))))) ;; SRFI 1 iota (define (iota count) (let loop ((i 1) (result '())) (if (> i count) (reverse result) (loop (+ i 1) (cons i result))))) (dummy (length (iota 1000000))) With Gambit version 4.6.9 $ gsc -:s -o list.c -c list.scm $ gsc -:s -o link.c -link list.c $ gcc -o list list.c link.c -ldl -lm -lgambc -lutil -L${GAMBITDIR}/lib/ -I${GAMBITDIR}/include/ $ ./list (time (length (iota 1000000))) 80 ms real time 79 ms cpu time (61 user, 18 system) 5 collections accounting for 55 ms real time (48 user, 6 system) 96000000 bytes allocated 23512 minor faults no major faults With Gambit version 4.7.4 $ gsc -:s -o list.c -c list.scm $ gsc -:s -o link.c -link list.c *** WARNING -- "$sc-put-cte" is not defined, *** referenced in: ("list.c") *** WARNING -- "$syntax-dispatch" is not defined, *** referenced in: ("list.c") *** WARNING -- "syntax-error" is not defined, *** referenced in: ("list.c") $ gcc -o list list.c link.c -ldl -lm -lgambc -lutil -L${GAMBITDIR}/lib/ -I${GAMBITDIR}/include/ $ ./list *** ERROR IN | list| -- Operator is not a PROCEDURE (#!unbound '#(syntax-object dummy ((top) #(ribcage #(dummy) #((top)) #(dummy)))) '#<procedure #2> '*top*) What is now the correct way to compile with macros in Gambit version 4.7.4 ? Emmanuel

2 2

Can't upload file to wiki
by Bradley Lucier 04 Mar '15

04 Mar '15

From this page: http://dynamo.iro.umontreal.ca/wiki/index.php/Special:Upload I get the message The upload directory (public) is not writable by the webserver. I'm logged in as bjlucier. Brad

1 0

Newbie Checking in
by Duke Normandin 04 Mar '15

04 Mar '15

Is this list active? Access to the archives seems to be hosed!! -- Duke ><>

4 9

Telling whether a file has been loaded, or a function defined?
by Bradley Lucier 04 Mar '15

04 Mar '15

Marc: I've got ##wr-meroon going pretty well, but if Meroon isn't loaded, then I get the following warnings when I use certain Meroon functions (obviously): *** WARNING -- "Class-fields" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "Class-name" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "Field-name" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "Mono-Field?" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "field-defined?" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "field-length" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "field-value" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") *** WARNING -- "object->class" is not defined, *** referenced in: ("/home/lucier/Downloads/gambit/lib/_gambc.c") I figure I can get around this by defining non-block dummy procedures for these Meroon-defined functions that will be replaced when Meroon is loaded. Perhaps you have a better solution. But is it possible to tell dynamically whether Meroon (or _meroon.o1, or whatever) has been loaded? Brad

1 1

DSLDI: 3rd Workshop on Domain-Specific Language Design and Implementation
by Tijs van der Storm 03 Mar '15

03 Mar '15

********************************************************************* FIRST CALL FOR TALK PROPOSALS DSLDI 2015 Third Workshop on Domain-Specific Language Design and Implementation July 7, 2015 Prague, Czech Republic Co-located with ECOOP http://2015.ecoop.org/track/dsldi-2015-papers ********************************************************************* Deadline for talk proposals: 2nd of April, 2015 If designed and implemented well, domain-specific languages (DSLs) combine the best features of general-purpose programming languages (e.g., performance) with high productivity (e.g., ease of programming). *** Workshop Goal *** The goal of the DSLDI workshop is to bring together researchers and practitioners interested in sharing ideas on how DSLs should be designed, implemented, supported by tools, and applied in realistic application contexts. We are both interested in discovering how already known domains such as graph processing or machine learning can be best supported by DSLs, but also in exploring new domains that could be targeted by DSLs. More generally, we are interested in building a community that can drive forward the development of modern DSLs. *** Workshop Format *** DSLDI is a single-day workshop and will consist of a series of short talks whose main goal is to trigger exchange of opinion and discussions. The talks should be on the topics within DSLDI's area of interest, which include but are not limited to the following ones: * DSL implementation techniques, including compiler-level and runtime-level solutions * utilization of domain knowledge for driving optimizations of DSL implementations * utilizing DSLs for managing parallelism and hardware heterogeneity * DSL performance and scalability studies * DSL tools, such as DSL editors and editor plugins, debuggers, refactoring tools, etc. * applications of DSLs to existing as well as emerging domains, for example graph processing, image processing, machine learning, analytics, robotics, etc. * practitioners reports, for example descriptions of DSL deployment i a real-life production setting *** Call for Submissions *** We solicit talk proposals in the form of short abstracts (max. 2 pages). A good talk proposal describes an interesting position, demonstration, or early achievement. The submissions will be reviewed on relevance and clarity, and used to plan the mostly interactive sessions of the workshop day. Publication of accepted abstracts and slides on the website is voluntary. * Deadline for talk proposals: April 2nd, 2015 * Notification: May 1st, 2015 * Workshop: July 7th, 2015 * Submission website: https://easychair.org/conferences/?conf=dsldi2015 *** Workshop Organization *** Organizers * Tijs van der Storm (storm(a)cwi.nl) CWI, The Netherlands * Sebastian Erdweg (erdweg(a)informatik.tu-darmstadt.de) TU Darmstadt, Germany Follow us on Twitter at https://twitter.com/wsdsldi Program committee * Emilie Balland * Martin Bravenboer (LogicBlox) * Hassan Chafi (Oracle Labs) * William Cook (UT Austin) * Shriram Krishnamurthi (Brown University) * Heather Miller (EPFL) * Bruno Oliveira (University of Hong Kong) * Cyrus Omar (CMU) * Richard Paige (University of York) * Tony Sloane (Macquarie University) * Emma Söderberg (Google) * Emma Tosch (University of Massachusetts, Amherst) * Jurgen Vinju (CWI) -- Researcher Centrum Wiskunde & Informatica (CWI) Master of Software Engineering Universiteit van Amsterdam (UvA) Dr. Tijs van der Storm @ Centrum Wiskunde & Informatica (CWI) Office: L225 | Phone: +31 (0)20 5924164 | Address: Science Park 123 P.O. Box 94079 | Postal code: 1090 GB | Amsterdam, The Netherlands

1 0

Help with starting bitset library
by Bradley Lucier 26 Fév '15

26 Fév '15

Marc: I started writing a bitset library to leverage the bitwise-* operations. I need some help in working with type macros, etc. Can you look at the simple code below and tell me how to express it in the right way? Also, your define-prim-nary implements a fold operation, which is much, much slower for bitwise operations than just 1. Making sure all arguments are exact ints. 2. Determining the size of the resulting bignum (to be possibly normalized to a fixnum later) from the sizes and signs of the arguments. 3. Allocating the final bignum and destructively modifying it based on the arguments. Should I look into that a bit? Brad The start of bitsets.scm follows. (##include "../lib/header.scm") ;; accessors and constructors are not inlined unless I add ;; the following declaration. ;; Is that why you write constructors and accessors as macros? (declare (inlining-limit 300)) (define-structure ##bitset body) (define-prim (##bitset-union bs1 bs2) (##define-macro (type-error-on-x) `'(1)) (##define-macro (type-error-on-y) `'(2)) (if (##bitset? x) (if (##bitset? y) (make-##bitset (##bitwise-ior (##bitset-body x) (##bitset-body y))) (type-error-on-y)) (type-error-on-x))) (define-prim-nary (bitset-union x y) (make-##bitset 0) (if (##bitset? x) x '(1)) (##bitset-union x y) macro-force-vars macro-no-check (##pair? ##fail-check-bitset))

1 0

Type predicates in _system.scm
by Bradley Lucier 25 Fév '15

25 Fév '15

Marc: A typical type predicate in _system.scm is (define-prim (##ratnum? obj) (and (##subtyped? obj) (##eq? (##subtype obj) (macro-subtype-ratnum)))) Should all these uses of ##eq? be changed to ##eqv? Also, it seems that you're set up to deserialize meroon objects, but not to serialize them. Is that easily fixed? Brad

2 2

Just so I got it right: ___device_tcp_client_read/write_raw_virt doing *len_done = 0; return ___FIX(___NO_ERR); makes Gambit's IO scheduler select() and reiterate?
by Mikael 25 Fév '15

25 Fév '15

Marc, Not super important at all but part of auditing, just to check that I understand this correctly: If a blocking Gambit IO operation (e.g. that would be a |read-subu8vector|/|write-subu8vector| with a positive |need| value or a |read-byte|/|write-byte|) is currently being invoked on a TCP port, and the respective ___device_tcp_client_read_raw_virt or ___device_tcp_client_write_raw_virt procedure invoked does *len_done = 0; return ___FIX(___NO_ERR); , then in response to it doing that, will Gambit's IO scheduler (presuming there's no constraint from TCP port timeout settings) wait for the socket to show readability or writability respectively using select() and then reiterate the procedure? E.g., * |read-byte| is invoked. * The TCP port's read buffer is empty so Gambit invokes ___device_tcp_client_read_raw_virt, and it does *len_done = 0; return ___FIX(___NO_ERR); . * In response to that, Gambit does select() for readability (not writability) on the socket, and after some while there socket is found to have more data available to be read. * In response to that, Gambit re-invokes ___device_tcp_client_read_raw_virt. This time it gives 5 bytes. The first of those bytes will become the |read-byte| call's result. Thanks, Mikael

2 2

macro-check-index
by Bradley Lucier 25 Fév '15

25 Fév '15

Marc: Where is macro-check-index defined, and, more importantly, what does it do? Brad

2 1