[Chicken-users] Final Call for Papers: ICFP 2017

[Lindsey Kuper]

  ICFP 2017
The 22nd ACM SIGPLAN International Conference on Functional Programming
 Oxford, United Kingdom
   http://icfp17.sigplan.org/
 Final Call for Papers
 
### Important dates

Submissions due:Monday, February 27, Anywhere on Earth
https://icfp17.hotcrp.com
Author response:Monday, April 17, 2017, 15:00 (UTC) -
Thursday, April 20, 2017, 15:00 (UTC)
Notification:   Monday, 1 May, 2017
Final copy due: Monday, 5 June 2017
Early registration: TBA
Conference: Monday, 4 September -
Wednesday, 6 September, 2017

### New this year

Those familiar with previous ICFP conferences should be aware of two
significant changes that are being introduced in 2017:

1. Papers selected for ICFP 2017 will be published as the ICFP 2017
issue of a new journal, Proceedings of the ACM on Programming Languages
(PACMPL), which replaces the previous ICFP conference proceedings. The
move to PACMPL will have two noticeable impacts on authors:

* A new, two-phase selection and reviewing process that conforms to
  ACM’s journal reviewing guidelines.

* A new, single-column format for submissions.

2. Authors of papers that are conditionally accepted in the first phase
of the reviewing process will have the option to submit materials for
Artifact Evaluation.

Further details on each of these changes are included in the following
text.

### Scope

ICFP 2017 seeks original papers on the art and science of functional
programming. Submissions are invited on all topics from principles to
practice, from foundations to features, and from abstraction to
application. The scope includes all languages that encourage functional
programming, including both purely applicative and imperative languages,
as well as languages with objects, concurrency, or parallelism. Topics
of interest include (but are not limited to):

  * *Language Design*: concurrency, parallelism, and distribution;
modules; components and composition; metaprogramming; type systems;
interoperability; domain-specific languages; and relations to
imperative, object-oriented, or logic programming.

  * *Implementation*: abstract machines; virtual machines;
interpretation; compilation; compile-time and run-time optimization;
garbage collection and memory management; multi-threading;
exploiting parallel hardware; interfaces to foreign functions,
services, components, or low-level machine resources.

  * *Software-Development Techniques*: algorithms and data structures;
design patterns; specification; verification; validation; proof
assistants; debugging; testing; tracing; profiling.

  * *Foundations*: formal semantics; lambda calculus; rewriting; type
theory; monads; continuations; control; state; effects; program
verification; dependent types.

  * *Analysis and Transformation*: control-flow; data-flow; abstract
interpretation; partial evaluation; program calculation.

  * *Applications*: symbolic computing; formal-methods tools; artificial
intelligence; systems programming; distributed-systems and web
programming; hardware design; databases; XML processing; scientific
and numerical computing; graphical user interfaces; multimedia and
3D graphics programming; scripting; system administration; security.

  * *Education*: teaching introductory programming; parallel
programming; mathematical proof; algebra.

Submissions will be evaluated according to their relevance, correctness,
significance, originality, and clarity. Each submission should explain
its contributions in both general and technical terms, clearly
identifying what has been accomplished, explaining why it is
significant, and comparing it with previous work. The technical content
should be accessible to a broad audience.

ICFP 2017 also welcomes submissions in two separate categories ---
Functional Pearls and Experience Reports --- that must be marked as
such at the time of submission and that need not report original
research results.  Detailed guidelines on both categories are given at
the end of this call.

Please contact the program chair if you have questions or are concerned
about the appropriateness of a topic.

### Preparation of submissions

ICFP 2017 will employ a lightweight double-blind reviewing process, as
described below.

**Deadline**: The deadline for submissions is Monday, February 27, 2017,
Anywhere on Earth ().
This deadline will be strictly enforced.

**Formatting**: (NOTE: NEW FORMAT REQUIREMENTS FOR ICFP 2017)
Submissions must be in PDF format, printable in black and white on US
Letter sized paper, and interpretable by common PDF tools. All
submissions must adhere to the "ACM Large" template that is available
(in both LaTeX and Word formats) from

Re: [Chicken-users] invalid encoded numeric literal (was: CHICKEN 4.12.0 rc2 available)

[Claude Marinier]

Allô,

I must apologize for my forgetfulness. I went through this six months ago.
Peter Bex helped me with this problem. The conclusion was that there is a
bad interaction between the locale (I am in Canada) and low level string &
number handling. The conclusion was as follows.

> I think the underlying problem (at least, for reading of numbers)
> has been fixed in CHICKEN 5; it will no longer use strtod or strtol[l]
> once we recompile and remove backwards bootstrap compatibility.

The whole story is on the Chicken Hackers mailing list. Using a 64-bit
version of MinGW is also involved in this. Since everything works well with
32-bit MinGW, it's easiest to wait for Chicken 5.

Thank you.

On 2017-02-15, Evan Hanson wrote:
> On 2017-02-14 21:44, Claude Marinier wrote:
> > I am trying to reproduce the error with the intent of poking around.
> > How can I tell 'csc' to keep the generated C?
>
> Use `csc -k` (for "keep").
>
> > By the way, right after building, I notice 'csi' behaves oddly.
> >
> > claude@HP MINGW64 ~/chicken-4.11.1/tests
> > $ csi
> > (* 1 2 3 4 5)
> > (exit)
> >
> > CHICKEN
> > (c) 2008-2016, The CHICKEN Team
> > (c) 2000-2007, Felix L. Winkelmann
> > Version 4.11.1 ((detached from 4.11.1)) (rev 116f42e)
> > windows-mingw32-x86-64 [ 64bit manyargs dload ptables ]
> > compiled 2016-09-12 on waldrop (Linux)
> >
> > 120
> >
> > claude@HP MINGW64 ~/chicken-4.11.1/tests
> > $
> >
> > This is unexpected. It looks like a terminal I/O problem. Is this known?
>
> Yeah, and I have a hunch it might be caused by the same underlying
> issue, but I'm not really sure. In short, `##sys#tty-port?`, which is
> used by by csi(1) to detect whether it's running in a terminal or not,
> fails from within the MSYS shell: peeking the leading byte of the port
> gives a non-zero value, which is unexpected.

-- 
Claude Marinier
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Chicken-users] 1st call for papers: Trends in Functional Programming, 19-21 june 2017, University of Kent, Canterbury

[Peter Achten]

-
C A L L   F O R   P A P E R S
-

 TFP 2017 ===

  18th Symposium on Trends in Functional Programming
   19-21 June, 2017
 University of Kent, Canterbury
   https://www.cs.kent.ac.uk/events/tfp17/index.html

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 2017 will be the main event of a pair of functional programming
events. TFP 2017 will be accompanied by the International Workshop on
Trends in Functional Programming in Education (TFPIE), which will take
place on 22 June.

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;
   * Inria Sophia-Antipolis (France) in 2015;
   * and Maryland (USA) in 2016.

For further general information about TFP please see the TFP homepage.
(http://www.tifp.org/).


== 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
symposium.

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 2017 program chairs, Scott Owens and Meng Wang.


== BEST PAPER AWARDS ==

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.


== SPONSORS ==

TBD

== PAPER SUBMISSIONS ==

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,