publicityifl | 24 May 21:13 2016

1st CfP: IFL 2016 (28th Symposium on Implementation and Application of Functional Languages)


Please, find below the first call for papers for IFL 2016.
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 2016 - Call for papers


KU Leuven, Belgium

In cooperation with ACM SIGPLAN

August 31 - September 2, 2016


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 2016 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.


Following the IFL tradition, IFL 2016 will use a post-symposium review process
to produce the formal proceedings. All participants of IFL 2016 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:

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

August 1: Submission deadline draft papers
August 3: Notification of acceptance for presentation
August 5: Early registration deadline
August 12: Late registration deadline
August 22: Submission deadline for pre-symposium proceedings
August 31 - September 2: IFL Symposium
December 1: Submission deadline for post-symposium proceedings
January 31, 2017: Notification of acceptance for post-symposium proceedings
March 15, 2017: 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:

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:


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 2016,
please contact the PC chair at tom.schrijvers <at> 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: Tom Schrijvers, KU Leuven, Belgium

- Sandrine Blazy, University of Rennes 1, France
- Laura Castro, University of A Coruña, Spain
- Jacques, Garrigue, Nagoya University, Japan
- Clemens Grelck, University of Amsterdam, The Netherlands
- Zoltan Horvath, Eotvos Lorand University, Hungary
- Jan Martin Jansen, Netherlands Defence Academy, The Netherlands
- Mauro Jaskelioff, CIFASIS/Universidad Nacional de Rosario, Argentina
- Patricia Johann, Appalachian State University, USA
- Wolfram Kahl, McMaster University, Canada
- Pieter Koopman, Radboud University Nijmegen, The Netherlands
- Shin-Cheng Mu, Academia Sinica, Taiwan
- Henrik Nilsson, University of Nottingham, UK
- Nikolaos Papaspyrou, National Technical University of Athens, Greece
- Atze van der Ploeg, Chalmers University of Technology, Sweden
- Matija Pretnar, University of Ljubljana, Slovenia
- Tillmann Rendel, University of Tübingen, Germany
- Christophe Scholliers, Universiteit Gent, Belgium
- Sven-Bodo Scholz, Heriot-Watt University, UK
- Melinda Toth, Eotvos Lorand University, Hungary
- Meng Wang, University of Kent, UK
- Jeremy Yallop, University of Cambridge, UK


The 28th IFL will be held in association with the Faculty of Computer Science,
KU Leuven, Belgium. Leuven is centrally located in Belgium and can be easily
reached from Brussels Airport by train (~15 minutes). The venue in the
Arenberg Castle park can be reached by foot, bus or taxi from the city center.
See the website for more information on the venue.
Chicken-users mailing list
Chicken-users <at>
Kristian Lein-Mathisen | 24 May 11:25 2016

extension loading in sqlite3 egg

Hi guys!

I wanted to use Spatialite with CHICKEN and though I'd use the sqlite3 egg. However, I quickly ran into a problem:

(execute db "select load_extension(\"mod_spatialite\");")
Error: (finalize!) not authorized: #<sqlite3:statement sql="">

Call history:

ff-testing.scm:1: ##sys#require  
type-checks.scm:54: ##sys#require  
sql-null.scm:14: constantly  
ff-testing.scm:3: sqlite3#open-database  
ff-testing.scm:7: sqlite3#first-row  
ff-testing.scm:7: print  
ff-testing.scm:9: sqlite3#execute   <--

In the sqlite3 command-line, this works fine. The solution was to enable extension loading which is not allowed by default:

However, this Sqlite3 function isn't available in the egg. Here's a rather trivial patch that adds it:

diff --git a/sqlite3.scm b/sqlite3.scm
index dd7f35f..ce039da 100644
--- a/sqlite3.scm
+++ b/sqlite3.scm
<at> <at> -69,6 +69,7 <at> <at>
+    enable-load-extension
 (import scheme chicken foreign)
<at> <at> -1034,4 +1035,7 <at> <at> EOS
+(define (enable-load-extension db enable?)
+  ((foreign-lambda sqlite3:status "sqlite3_enable_load_extension" sqlite3:database bool) db enable?))

Which now makes

(enable-load-extension db #t)
(execute db "select load_extension(\"mod_spatialite\");")

Work like a charm.

I'm not sure how to get this patch upstream. I don't think I have SVN access. So I was hoping the current sqlite3 maintainer wouldn't mind fixing this (eyes on you Thomas Chust! :D)!

Thank you,
Chicken-users mailing list
Chicken-users <at>
Christian Kellermann | 23 May 09:41 2016

Invitation to a weekend of scheme/lisp hacking

Dear picolisp readers,

As some of you know I am an active member of the CHICKEN scheme
community. For that I am organising a little "conference" / gathering
of interested scheme and lisp users in Nuremberg, Germany on September

As there's plenty of room available I broadened the invitation scope
to all interested schemers and lispers.

So if you want to be able to hack on a picolisp project and discuss
lispy stuff with other people afk you are invited to drop by.

I'd appreciate it if you add yourself to the list of attendees, so I
know how many people to expect. If you like drop me a mail so I can
reach you should there be some changes in plans.

You can read up the details here:

Hope to see a lot of you there!


May you be peaceful, may you live in safety, may you be free from
suffering, and may you live with ease.
Christian Kellermann | 20 May 12:53 2016

HEADS-UP! Next CHICKEN meetup <at> Nuremberg, Germany on the horizon!

Dear CHICKEN fans!

There will be a next CHICKEN conference comming up!

It will take place in Nuremberg, Germany, Europe, Planet Earth.

The date is to be choosen from the following three:

* July 22-24th
* September 9-11th
* September 23-25th

You can vote for a date here:

Please vote on the date *now* as I have to confirm it by Monday.
Sorry for being in a rush but the place is heavily used.

We will meet at the "Nachbarschaftshaus Gostenhof"
Adam-Klein-Straße 6
90429 Nürnberg

See for how to get there with public transport.

I will open up a wiki page ASAP including suggestions on where to
stay. Chickenistas that have been to the previous event in Nuremberg
might recall whether they liked their hotel and add suggestions as

The event will start around 16:00 on the Friday and we will leave on
sunday evening (~ 20:00).

The program (*laugh*) for the event will have to be made up either on
the wiki or as we go along.

The area around the venue has lots of nice food places, restaurants,
bars and Biergarten, so we will not starve. The local cafeteria will
provide us with soft drinks and coffee, even food if desired.

Nuremberg is reachable either by train or plane (airport code is NUE).

If you need any further assistance or have any questions don't
hesitate to ask.

I hope I will see you all there!

Kind regards,


May you be peaceful, may you live in safety, may you be free from
suffering, and may you live with ease.
Kooda | 18 May 21:25 2016

[PATCH] (low priority) Make locative-ref inlineable (ticket #1260)


I was browsing and found this low hanging bug so I gave it a shot.
I hope I didn’t mess up too much.

From fcba39930dcb56cc16500531fa37cf0fe0a4aaef Mon Sep 17 00:00:00 2001
From: Kooda <kooda <at>>
Date: Wed, 18 May 2016 10:48:58 +0200
Subject: [PATCH] Make locative-ref inlineable (ticket #1260)

- Deprecate C_localtive_ref
- Add C_a_i_locative_ref
- Add a compiler rewrite for locative-ref
- Add a specialization for locative-ref on locatives
 c-platform.scm |  2 +-
 chicken.h      |  3 ++-
 lolevel.scm    |  3 ++-
 runtime.c      | 27 ++++++++++++++++++++++++++-
 types.db       |  4 +++-
 5 files changed, 34 insertions(+), 5 deletions(-)

diff --git a/c-platform.scm b/c-platform.scm
index b2f6629..3e7548b 100644
--- a/c-platform.scm
+++ b/c-platform.scm
 <at>  <at>  -533,7 +533,6  <at>  <at> 
 (rewrite 'call-with-values 13 2 "C_call_with_values" #t)
 (rewrite '##sys#call-with-values 13 2 "C_u_call_with_values" #f)
 (rewrite '##sys#call-with-values 13 2 "C_call_with_values" #t)
-(rewrite 'locative-ref 13 1 "C_locative_ref" #t)
 (rewrite '##sys#continuation-graft 13 2 "C_continuation_graft" #t)

 (rewrite 'caar 2 1 "C_u_i_caar" #f)
 <at>  <at>  -874,6 +873,7  <at>  <at> 
 (rewrite 'address->pointer 16 1 "C_a_i_address_to_pointer" #f 2)
 (rewrite 'pointer->address 16 1 "C_a_i_pointer_to_address" #f words-per-flonum)
 (rewrite 'pointer+ 16 2 "C_a_u_i_pointer_inc" #f 2)
+(rewrite 'locative-ref 16 1 "C_a_i_locative_ref" #t words-per-flonum)

 (rewrite 'pointer-u8-ref 2 1 "C_u_i_pointer_u8_ref" #f)
 (rewrite 'pointer-s8-ref 2 1 "C_u_i_pointer_s8_ref" #f)
diff --git a/chicken.h b/chicken.h
index 160d40d..3f00956 100644
--- a/chicken.h
+++ b/chicken.h
 <at>  <at>  -1831,7 +1831,7  <at>  <at>  C_fctexport C_cpsproc(C_register_finalizer) C_noret;
 C_fctexport C_cpsproc(C_set_dlopen_flags) C_noret;
 C_fctexport C_cpsproc(C_dload) C_noret;
 C_fctexport C_cpsproc(C_become) C_noret;
-C_fctexport C_cpsproc(C_locative_ref) C_noret;
+C_fctexport C_cpsproc(C_locative_ref) C_noret; /* DEPRECATED */
 C_fctexport C_cpsproc(C_call_with_cthulhu) C_noret;
 C_fctexport C_cpsproc(C_copy_closure) C_noret;
 C_fctexport C_cpsproc(C_dump_heap_state) C_noret;
 <at>  <at>  -1923,6 +1923,7  <at>  <at>  C_fctexport C_word C_fcall C_i_char_greaterp(C_word x, C_word y) C_regparm;
 C_fctexport C_word C_fcall C_i_char_lessp(C_word x, C_word y) C_regparm;
 C_fctexport C_word C_fcall C_i_char_greater_or_equal_p(C_word x, C_word y) C_regparm;
 C_fctexport C_word C_fcall C_i_char_less_or_equal_p(C_word x, C_word y) C_regparm;
+C_fctexport C_word C_fcall C_a_i_locative_ref(C_word **a, int c, C_word loc) C_regparm;
 C_fctexport C_word C_fcall C_i_locative_set(C_word loc, C_word x) C_regparm;
 C_fctexport C_word C_fcall C_i_locative_to_object(C_word loc) C_regparm;
 C_fctexport C_word C_fcall C_a_i_make_locative(C_word **a, int c, C_word type, C_word object, C_word
index, C_word weak) C_regparm;
diff --git a/lolevel.scm b/lolevel.scm
index 7a1724f..1ac2eed 100644
--- a/lolevel.scm
+++ b/lolevel.scm
 <at>  <at>  -298,7 +298,8  <at>  <at>  EOF

 (define locative-ref
-   (##core#primitive "C_locative_ref") 
+   (lambda (loc)
+     (##core#inline_allocate ("C_a_i_locative_ref" 4) loc))
    "(locative-ref loc)"))

diff --git a/runtime.c b/runtime.c
index 113e26d..c61d5d2 100644
--- a/runtime.c
+++ b/runtime.c
 <at>  <at>  -8780,7 +8780,7  <at>  <at>  C_regparm C_word C_fcall C_a_i_make_locative(C_word **a, int c, C_word type, C_w
   return (C_word)loc;

 void C_ccall C_locative_ref(C_word c, C_word *av)
 <at>  <at>  -8816,6 +8816,31  <at>  <at>  void C_ccall C_locative_ref(C_word c, C_word *av)

+C_regparm C_word C_fcall C_a_i_locative_ref(C_word **a, int c, C_word loc)
+  C_word *ptr;
+  if(C_immediatep(loc) || C_block_header(loc) != C_LOCATIVE_TAG)
+    barf(C_BAD_ARGUMENT_TYPE_ERROR, "locative-ref", loc);
+  ptr = (C_word *)C_block_item(loc, 0);
+  if(ptr == NULL) barf(C_LOST_LOCATIVE_ERROR, "locative-ref", loc);
+  switch(C_unfix(C_block_item(loc, 2))) {
+  case C_SLOT_LOCATIVE: return *ptr;
+  case C_CHAR_LOCATIVE: return C_make_character(*((char *)ptr));
+  case C_U8_LOCATIVE: return C_fix(*((unsigned char *)ptr));
+  case C_S8_LOCATIVE: return C_fix(*((char *)ptr));
+  case C_U16_LOCATIVE: return C_fix(*((unsigned short *)ptr));
+  case C_S16_LOCATIVE: return C_fix(*((short *)ptr));
+  case C_U32_LOCATIVE: return C_unsigned_int_to_num(a, *((C_u32 *)ptr));
+  case C_S32_LOCATIVE: return C_int_to_num(a, *((C_s32 *)ptr));
+  case C_F32_LOCATIVE: return C_flonum(a, *((float *)ptr));
+  case C_F64_LOCATIVE: return C_flonum(a, *((double *)ptr));
+  default: panic(C_text("bad locative type"));
+  }

 C_regparm C_word C_fcall C_i_locative_set(C_word loc, C_word x)
diff --git a/types.db b/types.db
index b4a3887..b1165c0 100644
--- a/types.db
+++ b/types.db
 <at>  <at>  -1502,7 +1502,9  <at>  <at> 
 (extended-procedure? (#(procedure #:clean) extended-procedure (*) boolean))
 (free (#(procedure #:clean #:enforce) free (pointer) undefined))
 (locative->object (#(procedure #:clean #:enforce) locative->object (locative) *))
-(locative-ref (#(procedure #:clean #:enforce) locative-ref (locative) *))
+(locative-ref (#(procedure #:clean #:enforce) locative-ref (locative) *)
+	      ((locative)
+	       (##core#inline_allocate ("C_a_i_locative_ref" 4) #(1))))
 (locative-set! (#(procedure #:enforce) locative-set! (locative *) *))
 (locative? (#(procedure #:pure #:predicate locative) locative? (*) boolean))
 (make-locative (#(procedure #:clean #:enforce) make-locative (* #!optional fixnum) locative))


Chicken-users mailing list
Chicken-users <at>
Matt Welland | 15 May 02:46 2016

Re: [ANN] CHICKEN 4.11.0 release candidate 2 available

Operating system: Ubuntu 14.04
Hardware platform: x86-64
C Compiler: GCC 4.8.4
Installation works?: yes
Tests work?: Did not run tests
Installation of eggs works?: yes

The testsuite for my pet project, Megatest, passes with Chicken 4.11rc2. I did see the IUP based dashboard die with an assertion but I lost the message and it has been running fine after a clean recompile without -debug-info. I did compile with -debug-info and used feathers to step through some code successfully. It is possible that I had a mix of .o files, some with -debug-info and some without and possibly that caused the assertion (just speculating).

The following eggs are referenced in the source. Quite a few, but not all, are exercised in the testsuite:


All in all, I'm ready to switch to 4.11. Thanks and kudos to the Chicken team.

The eggs I installed (using this Makefile

matchable readline apropos base64 regex-literals format regex-case test coops trace csv \ dot-locking posix-utils posix-extras directory-utils hostinfo tcp-server rpc csv-xml fmt \ json md5 awful http-client spiffy uri-common intarweb spiffy-request-vars pathname-expand \ spiffy-directory-listing ssax sxml-serializer sxml-modifications sql-de-lite \ srfi-19 refdb ini-file sparse-vectors z3 call-with-environment-variables hahn linenoise \ crypt parley

+ iup canvas-draw logpro

On Thu, Apr 28, 2016 at 11:39 AM, Peter Bex <peter <at>> wrote:
Hello all,

The second release candidate for CHICKEN 4.11.0 is now available for download:

This tarball has the following SHA-2 checksum:

The list of changes since 4.10.0 is available here:

The changes since the previous release candidate (rc1) are as follows:
- On 32-bit systems, the debugger client used incorrect printf format
   strings, resulting in invalid data used for the protocol.  This made
   debugging of programs running on 32-bit systems impossible (#1279).
- Under Mac OS X, "make check" failed in a non-installed CHICKEN due to
   the new "System Integrity Protection" breaking DYLD_LIBRARY_PATH in
   all processes that are invoked through /bin/sh (#1277).
   Thanks to J Irving for reporting this, and Jim Ursetto for creating
   and testing the fix.
- On 64-bit architectures where "char" defaults to unsigned (e.g. ARM64),
   negative signed fixnum literals embedded inside other literals would
   be decoded incorrectly (#1280).  Thanks to Alex Shendi for reporting
   this and testing the fix.
- When initializing a new egg repository, if the destination directory
   does not exist, chicken-install would write all files to the target
   as if it were a file.  Thanks to "LemonBoy" for reporting this and
   creating a fix.
- Stack checks inserted by the compiler would incorrectly trigger stack
   overflow errors after receiving a signal (#1283).  Thanks to
   "LemonBoy" for helping to track down this error.

These last-minute changes are very important for the stability of the
system, so we are very happy they made it in.  However, due to the impact
of especially the latter, we would ask you all to help us test the new
release candidate as thoroughly as the first one.

As usual, an easy way to test this RC is as follows:

$ make PLATFORM=<platform> PREFIX=<some dir> install check
$ <some dir>/bin/chicken-install pastiche

If you want to build CHICKEN with a compiler other than the default one,
just use C_COMPILER=<the compiler> (e.g., C_COMPILER=clang) on the make

Of course, feel free to explore other supported build options (see the
README file for more information) and actually use CHICKEN 4.11.0rc2 for
your software.

If you can, please let us know the following information about the
environment you tested the RC tarball on:

Operating system: (e.g., FreeBSD 10.1, Debian 8, Windows 7 mingw-msys)
Hardware platform: (e.g., x86, x86-64, PPC)
C Compiler: (e.g., GCC 4.9.2, clang 3.6)
Installation works?: yes or no
Tests work?: yes or no
Installation of eggs works?: yes or no

Thanks in advance!


Chicken-users mailing list
Chicken-users <at>

Chicken-users mailing list
Chicken-users <at>
Matt Welland | 14 May 23:28 2016

Is there a replacement for expand-home-path in 4.11rc2?

I used resolve-pathname from posix-extras and expand-home-path is no longer available. Is this intended to be fixed? If it is not to be fixed what is the suggested way to expand a path, use readlink -f?

Warning (#<thread: runs:run-tests-queue>): in thread: unbound variable: ##sys#expand-home-path

    Call history:

    db.scm:113: ##sys#call-with-values     
    db.scm:2632: conc     
    db.scm:2627: sqlite3#for-each-row     
    db.scm:119: db:done-with     
    db.scm:95: sqlite3#database?     
    db.scm:97: mutex-lock!     
    db.scm:100: current-milliseconds     
    db.scm:102: mutex-unlock!     
    db.scm:113: k750     
    db.scm:113: g754     
    api.scm:107: k10     
    api.scm:107: g14     
    rmt.scm:240: current-milliseconds     
    launch.scm:947: hash-table-set!     
    launch.scm:950: file-exists?     
    launch.scm:951: posix-extras#resolve-pathname         
Chicken-users mailing list
Chicken-users <at>
Claude Marinier | 5 May 17:21 2016

chicken 4.11.0rc2, installing numbers, "Warning: excluded identifier doesn't exist in module scheme: rationalize"

Good morning,

I installed the numbers egg. It succeeded but gives warnings. Building the application produces the same six warning messages. Should I be concerned about this?

Here is the transcript.

chicken-install numbers
[sudo] password for claude:
retrieving ...
connecting to host "", port 80 ...
requesting "/henrietta.cgi?name=numbers&mode=default" ...
reading response ...
HTTP/1.1 200 OK
Date: Thu, 05 May 2016 15:11:28 GMT
Server: Apache/2.2.29 (Unix) DAV/2 SVN/1.8.10 PHP/5.4.32 mod_fastcgi/2.4.6
Connection: close
Transfer-Encoding: chunked
Content-Type: text/plain
reading chunks ........
reading files ...
 numbers located at /tmp/temp3f65.20630/numbers
checking platform for `numbers' ...
checking dependencies for `numbers' ...
install order:
installing numbers:4.6 ...
changing current directory to /tmp/temp3f65.20630/numbers
  '/usr/local/bin/csi' -bnq -setup-mode -e "(require-library setup-api)" -e "(import setup-api)" -e "(setup-error-handling)" -e "(extension-name-and-version '(\"numbers\" \"4.6\"))" 'numbers.setup'
  '/usr/local/bin/csc' -feature compiling-extension -setup-mode    -C -fexcess-precision=standard -s -O3 numbers.scm -j numbers

Warning: excluded identifier doesn't exist in module scheme: rationalize

Warning: excluded identifier doesn't exist in module scheme: make-rectangular

Warning: excluded identifier doesn't exist in module scheme: make-polar

Warning: excluded identifier doesn't exist in module chicken: random

Warning: excluded identifier doesn't exist in module chicken: randomize

Warning: excluded identifier doesn't exist in module chicken: conj
  '/usr/local/bin/csc' -feature compiling-extension -setup-mode    -s -O3 numbers.import.scm
  cp -r '' '/usr/local/lib/chicken/8/'
  chmod a+r '/usr/local/lib/chicken/8/'
  cp -r '' '/usr/local/lib/chicken/8/'
  chmod a+r '/usr/local/lib/chicken/8/'
  cp -r 'numbers-syntax.scm' '/usr/local/lib/chicken/8/numbers-syntax.scm'
  chmod a+r '/usr/local/lib/chicken/8/numbers-syntax.scm'
  chmod a+r '/usr/local/lib/chicken/8/numbers.setup-info'

Claude Marinier
Chicken-users mailing list
Chicken-users <at>
Jeremy Steward | 3 May 06:37 2016

New Eggs: SRFI-113 and SRFI-128

Hello all,

Over the weekend I've taken John Cowan's work on SRFI-113 (Sets and
Bags) and SRFI-128 (Comparators (reduced)) and packaged them up nicely
into eggs. The URLs are below, I think it'd be great if we could add
them to the coop. Salmonella reports all tests passing and
installation working correctly, with one caveat: Since SRFI-113
depends on SRFI-128, I cannot yet run Salmonella independently on
SRFI-113, however I expect there to be no errors.

I plan to package SRFI-133 (Vector Library (R7RS-compatible)),
SRFI-121 (Generators), and SRFI-127 (Lazy Sequences) as time permits
over the next couple of weeks. Any feedback into which (if any) new
SRFI's that haven't been packaged for CHICKEN are desired would be
great, so I can focus on those additionally, provided the work isn't
too severe.

Best regards, and thanks again to the work that John Cowan, Arthur
Gleckler, and the SRFI committee has put in to make these libraries

Jeremy Steward

Peter Achten | 2 May 08:59 2016

[TFP'16] call for participation

              C A L L   F O R   P A R T I C I P A T I O N

                     ======== TFP 2016 ===========

           17th Symposium on Trends in Functional Programming
                            June 8-10, 2016
                  University of Maryland, College Park
                          Near Washington, DC

The symposium on Trends in Functional Programming (TFP) is an
international forum for researchers with interests in all aspects of
functional programming, taking a broad view of current and future
trends in the area. It aspires to be a lively environment for
presenting the latest research results, and other contributions (see
below). Authors of draft papers will be invited to submit revised
papers based on the feedback receive at the symposium.  A
post-symposium refereeing process will then select a subset of these
articles for formal publication.

TFP 2016 will be the main event of a pair of functional programming
events. TFP 2016 will be accompanied by the International Workshop on
Trends in Functional Programming in Education (TFPIE), which will take
place on June 7nd.


TFP 2016 is pleased to announce keynote talks by the following two
invited speakers:

* Ronald Garcia, University of British Columbia: "Static and Dynamic
   Type Checking: A Synopsis"

* Steve Zdancewic, University of Pennsylvania: "Type- and
   Example-Driven Program Synthesis"


The TFP symposium is the heir of the successful series of Scottish
Functional Programming Workshops. Previous TFP symposia were held in
    * Edinburgh (Scotland) in 2003;
    * Munich (Germany) in 2004;
    * Tallinn (Estonia) in 2005;
    * Nottingham (UK) in 2006;
    * New York (USA) in 2007;
    * Nijmegen (The Netherlands) in 2008;
    * Komarno (Slovakia) in 2009;
    * Oklahoma (USA) in 2010;
    * Madrid (Spain) in 2011;
    * St. Andrews (UK) in 2012;
    * Provo (Utah, USA) in 2013;
    * Soesterberg (The Netherlands) in 2014;
    * and Inria Sophia-Antipolis (France) in 2015.
For further general information about TFP please see the TFP homepage.

== SCOPE ==

The symposium recognizes that new trends may arise through various
routes.  As part of the Symposium's focus on trends we therefore
identify the following five article categories. High-quality articles
are solicited in any of these categories:

Research Articles: leading-edge, previously unpublished research work
Position Articles: on what new trends should or should not be
Project Articles: descriptions of recently started new projects
Evaluation Articles: what lessons can be drawn from a finished project
Overview Articles: summarizing work with respect to a trendy subject

Articles must be original and not simultaneously submitted for
publication to any other forum. They may consider any aspect of
functional programming: theoretical, implementation-oriented, or
experience-oriented.  Applications of functional programming
techniques to other languages are also within the scope of the

Topics suitable for the symposium include, but are not limited to:

      Functional programming and multicore/manycore computing
      Functional programming in the cloud
      High performance functional computing
      Extra-functional (behavioural) properties of functional programs
      Dependently typed functional programming
      Validation and verification of functional programs
      Debugging and profiling for functional languages
      Functional programming in different application areas:
        security, mobility, telecommunications applications, embedded
        systems, global computing, grids, etc.
      Interoperability with imperative programming languages
      Novel memory management techniques
      Program analysis and transformation techniques
      Empirical performance studies
      Abstract/virtual machines and compilers for functional languages
      (Embedded) domain specific languages
      New implementation strategies
      Any new emerging trend in the functional programming area

If you are in doubt on whether your article is within the scope of
TFP, please contact the TFP 2016 program chair, David Van Horn.


To reward excellent contributions, TFP awards a prize for the best paper
accepted for the formal proceedings.

TFP traditionally pays special attention to research students,
acknowledging that students are almost by definition part of new
subject trends. A student paper is one for which the authors state
that the paper is mainly the work of students, the students are listed
as first authors, and a student would present the paper. A prize for
the best student paper is awarded each year.

In both cases, it is the PC of TFP that awards the prize. In case the
best paper happens to be a student paper, that paper will then receive
both prizes.


TFP is financially supported by CyberPoint, Galois, Trail of Bits, and
the University of Maryland Computer Science Department.


Acceptance of articles for presentation at the symposium is based on a
lightweight peer review process of extended abstracts (4 to 10 pages
in length) or full papers (20 pages). The submission must clearly
indicate which category it belongs to: research, position, project,
evaluation, or overview paper. It should also indicate which authors
are research students, and whether the main author(s) are students.  A
draft paper for which ALL authors are students will receive additional
feedback by one of the PC members shortly after the symposium has
taken place.

We use EasyChair for the refereeing process. Papers must be submitted at:

Papers must be written in English, and written using the LNCS
style. For more information about formatting please consult the
Springer LNCS web site:


Submission of draft papers:     April 25, 2016
Notification:                   May 2, 2016
Registration:                   May 13, 2016
TFP Symposium:                  June 8-10, 2016
Student papers feedback:        June 14, 2016
Submission for formal review:   July 14, 2016
Notification of acceptance:     September 14, 2016
Camera ready paper:             October 14, 2016


Amal Ahmed              Northeastern University (US)
Nada Amin               École Polytechnique Fédérale de Lausanne (CH)
Kenichi Asai            Ochanomizu University (JP)
Małgorzata Biernacka    University of Wroclaw (PL)
Laura Castro            University of A Coruña (ES)
Ravi Chugh              University of Chicago (US)
Silvia Ghilezan         University of Novi Sad (SR)
Clemens Grelck          University of Amsterdam (NL)
John Hughes             Chalmers University of Technology (SE)
Suresh Jagannathan      Purdue University (US)
Pieter Koopman          Radboud University Nijmegen (NL)
Geoffrey Mainland       Drexel University (US)
Chris Martens           University of California, Santa Cruz (US)
Jay McCarthy            University of Massachusetts, Lowell (US)
Heather Miller          École Polytechnique Fédérale de Lausanne (CH)
Manuel Serrano          INRIA, Sophia-Antipolis (FR)
Scott Smith             Johns Hopkins University (US)
Éric Tanter             University of Chile (CL)
David Van Horn (Chair)  University of Maryland (US)
Niki Vazou              University of California, San Diego (US)
Stephanie Weirich       University of Pennsylvania (US)

Chicken-users mailing list
Chicken-users <at>
Kooda | 1 May 14:59 2016

Re: [Chicken-announce] [ANN] CHICKEN 4.11.0 release candidate 2 available

Operating system: Alpine Linux (musl libc)
Hardware platform: x86-64
C Compiler: gcc 5.3.0
Installation works?: Yes
Tests work?: Yes
Installation of eggs works?: Yes (pastiche)

Operating system: Alpine Linux (musl libc)
Hardware platform: armv7
C Compiler: gcc 5.3.0
Installation works?: Yes
Tests work?: Yes
Installation of eggs works?: Yes (spiffy)