Skip to main content
Instructions for contributors

Papers may describe original technical work, survey an area, or present a tutorial; and may be either short or long. Anything related to functional programming is of interest, including: foundations (semantics, abstract interpretation, lambda calculi, rewriting, logic, type theory, category theory); implementation (compilation, architectures, parallelism, garbage collection, I/O, debugging, profiling); linguistics (pure and impure language features, non-determinism, side effects, logical variables, relation to other programming paradigms, proofs about programs, program transformation, program synthesis, partial evaluation); applications (applications programs, practical experience, programming techniques, prototyping).

Book reviews

Books for review, or suggestions for reviews, should be sent to the reviews editor Simon Thompson.

Submission of manuscripts

General advice for authors is available here

Manuscripts for consideration for the Journal of Functional Programming should be submitted electronically, using the Manuscript Central System. This system will allow authors to benefit from faster review and earlier, online publication. The system will accept PDF files, which are the preferred form for submission; most other files types will be automatically converted directly into PDF, but it will not compile TeX or LaTeX files. Source files are required for any paper accepted for publication. Authors who are unable to submit online should contact the Editorial Office for assistance. Authors may want to consult the guidelines we offer to JFP referees, to get an idea of the criteria that will be applied by referees.
The Journal of Functional Programming encourages authors of workshop and conference papers to submit enhanced versions of the same work to JFP. Typically, the version submitted to JFP should contain additional discussion, examples, or proofs. Only if a workshop or conference paper is exceptionally well presented and complete is it suitable for journal publication without significant revision. If another publisher holds copyright on an earlier version of an article, the enhanced version must differ sufficiently so that the author can assign copyright to Cambridge University Press.

Submissions from arXiv

Authors who have used arXiv as a preprint server are able to submit their paper directly to JFP. In order to do this the arXiv ID number needs to be uploaded during the submission process.

Electronic manuscripts

The publisher encourages submission of manuscripts written in LaTeX which can be used for direct typesetting.
Authors using LaTeX should use the JFP LaTeX class file. This, along with related files, can be found here (zip file). If you have difficulties obtaining these files, there is a help-line available via e-mail. While use of the JFP LaTeX class file is preferred, plain LaTeX or TeX files can also be accepted.

Web-accessible accompanying material for your paper

For some (but not all) papers it may be useful to accompany the paper with source code, data, proofs, or other material, in web-readable form. You are encouraged to supply such supplements, which JFP will make permanently accessible over the Web. They should be considered as an element of the submission and so be subject to the review process. Find out more here.

Layout of manuscripts

Manuscripts should begin with an abstract of not more than 300 words. Papers should conform to a good standard of English prose; please consult a style guide such as 'The Elements of Style' by Strunk and White, Macmillan, New York. It is encouraged to present programs in one of two styles: either with identifiers in italic and keywords in bold, or entirely in a fixed-width teletype font. Do not begin a sentence with a symbol or identifier name. Please supply Web URLs for the home page of each of the authors of the paper. These are used when generating the JFPbibliography and author index. People searching the JFP indexes will then be able to find their way to your home page easily.


The Harvard system of references should be used. Citations are by author's surname and year of publication, and may stand either as a noun phrase (e.g., "Curry (1933)") or as a parenthetical note (e.g., "(Curry 1933)''). List references at the end of the text in alphabetical order. A typical entry is: Curry, H. B. (1933) Apparent variables from the standpoint of mathematical logic, Ann. of Math., 34 (2): 381-404. In the case of a reference to a conference, please give its year and location. There is no need to give the location of a publisher.
Use the jfp.bst file in conjunction with your bibtex database.


Figures and captions should be included as .eps files within the LaTeX source with the usual figure environment. Figures will appear in black and white in the print version whether or not they are supplied in colour. However, in the online version they can be reproduced in colour. Colour figures should be supplied in CMYK format. For more information regarding the supply of illustrations, click here.


Only typographical or factual errors may be changed at the proof stage. The publisher reserves the right to charge for correction of non-typographical errors. No page charge is made. JFP's policy is to follow the spelling convention (American or British) of the author(s).


No paper offprints are provided, but the corresponding author will be sent the pdf of the published article.

Publication Ethics

The Journal of Functional Programming is committed to respect high standards of ethics in the editorial and reviewing process and adheres to the code of conduct for editors enacted by the Committee of Publication Ethics (COPE). The journal wishes to make sure that contributors respect these standards. The guidelines on good publication practice for authorship can be found here. During the electronic submission process, authors will be asked to follow these guidelines and declare any potential conflicts of interest. For further information on publication ethics at Cambridge University Press please see here.

Cambridge Language Editing Service

We suggest that authors whose first language is not English have their manuscripts checked by a native English speaker before submission. This is optional but will help to ensure that any submissions that reach peer review can be judged exclusively on academic merit. We offer a Cambridge service which you can find out more about here, and suggest that authors make contact as appropriate. Please note that use of language editing services is voluntary and at the author’s own expense. Use of these services does not guarantee that the manuscript will be accepted for publication nor does it restrict the author to submitting to a Cambridge-published journal.

Video Abstracts

JFP invites all authors of accepted papers to submit a video abstract. The goal of such an abstract is to highlight the essential novelties and to get the viewer to read the paper. So when you design the video, ask yourself how to reach a potential viewer:

  • what is the problem (area)
  • what is the key idea
  • what is a good graphical-visual way to bring across the idea
  • where should the video refer to the paper for details

Note: Videos may be submitted only after a paper is accepted. They are not part of the reviewing process; reviewers will continue to judge submissions solely on their scientific content.

The video can take any form that the authors would like as long as it focuses on the content of the paper. For example,

  • a video may present a slide show with a voice over, like those used in conferences
  • a video may show carefully edited excerpts from a conference video, though authors must respect the copyright notices on published conference videos
  • the authors may produce a video specifically for JFP at their home institutions, using whatever resources are made available there.   

Papers with videos will be posted in a specially advertised section (in addition to the usual entry as part of a JFP volume), and the videos will be freely accessible.

A video must be no longer than 10 minutes.

Currently accepted formats are: mp4.