From: Ralf Hinze <ralf@informatik.uni-bonn.de>
To: amast@cs.utwente.nl, appsem@cs.chalmers.se, caml-list@inria.fr,
categories@mta.ca, ccp@sics.se, church-announce@types.bu.edu,
clean-list@cs.kun.nl, clp@comp.nus.edu.sg,
comlab@comlab.ox.ac.uk, compunode@dfki.de, concurrency@cwi.nl,
eacsl@dimi.uniud.it, eatcs-it@cs.unibo.it,
erlang-questions@erlang.org, formal-methods@cs.uidaho.edu,
forum@jsoftware.com, generic-haskell@generic-haskell.org,
grin@di.unipi.it, gulp@di.unipi.it, ipalist@win.tue.nl,
lics@research.bell-labs.com, logic@CS.Cornell.EDU,
logic@theory.lcs.mit.edu, lprolog@cis.upenn.edu,
lprolog@cs.umn.edu, mercury-users@cs.mu.OZ.AU,
mlnet@swi.psy.uva.nl, pl-seminar@ccs.neu.edu,
plt-scheme@fast.cs.utah.edu, prolog-vendors@sics.se,
relmics-list@heraklit.informatik.unibw-muenchen.de,
rewriting@ens-lyon.fr, sicstus-users@sics.se,
skeletons@dcs.ed.ac.uk, theorem-provers@ai.mit.edu,
theorynt@listserv.nodak.edu, users@mozart-oz.org
Subject: [Caml-list] Final CFP: JFP Special Issue on Functional Pearls
Date: Mon, 5 Aug 2002 08:03:52 +0200 [thread overview]
Message-ID: <200205031501.42520.ralf@informatik.uni-bonn.de> (raw)
The deadline is approaching...
Write a pearl today!
============================================================================
FINAL CALL FOR PAPERS
Special Issue on Functional Pearls
http://www.informatik.uni-bonn.de/~ralf/necklace.html
[Deadline: 31 August 2002]
============================================================================
Wer die Perle in Händen hält,
fragt nicht nach der Muschel.
- Peter Benary
A special issue of the Journal of Functional Programming will be
devoted to Functional Pearls. The submission deadline is 31 August
2002.
Scope
-----
Do you have a paper that is small, rounded and enjoyable to read?
Please consider submitting it to the Special Issue on Functional
Pearls, as we intend to string a shiny necklace. If you don't have a
pearl, write one today! Papers can be on any subject connected to
functional programming. A pearl is typically around 8 pages, though
there is no strict page limit. The special issue also welcomes
tutorial or educational papers in a broad sense.
Submission details
------------------
Manuscripts should be unpublished works and not submitted elsewhere.
Revised and polished versions of papers published in conference
proceedings that have not appeared in archival journals are eligible
for submission. All submissions will be reviewed according to the
usual standards of scholarship and judged by elegance of development
and clarity of expression. One of the main reviewers will be Richard
Bird, the editor of JFP's regular Functional Pearls column.
Deadline for submission: 31 August 2002
Notification of acceptance or rejection: 30 November 2002
Revised version due: 31 January 2003
Submissions should be sent to the Guest Editor (see address below),
with a copy to Nasreen Ahmad (nasreen@dcs.gla.ac.uk). Submitted
articles should be sent in PDF or Postscript format, preferably
gzipped and uuencoded. The use of the JFP style files is strongly
recommended. In addition, please send, as plain text, title, abstract
(if any), and contact information. The submission deadline is 31
August 2002. Authors will be notified of acceptance or rejection by
30 November 2002. Revised versions are due on 31 January 2003. For
other submission details, please consult an issue of the Journal of
Functional Programming or see the Journal's web page at
http://www.dcs.gla.ac.uk/jfp/.
Guest Editor
------------
Ralf Hinze
Institut für Informatik III
Universität Bonn
Römerstraße 164
53117 Bonn, Germany
Telephone: +49 (2 28) 73 - 45 35
Fax: +49 (2 28) 73 - 43 82
Email: ralf@informatik.uni-bonn.de
WWW: http://www.informatik.uni-bonn.de/~ralf/
============================================================================
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2002-08-05 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200205031501.42520.ralf@informatik.uni-bonn.de \
--to=ralf@informatik.uni-bonn.de \
--cc=amast@cs.utwente.nl \
--cc=appsem@cs.chalmers.se \
--cc=caml-list@inria.fr \
--cc=categories@mta.ca \
--cc=ccp@sics.se \
--cc=church-announce@types.bu.edu \
--cc=clean-list@cs.kun.nl \
--cc=clp@comp.nus.edu.sg \
--cc=comlab@comlab.ox.ac.uk \
--cc=compunode@dfki.de \
--cc=concurrency@cwi.nl \
--cc=eacsl@dimi.uniud.it \
--cc=eatcs-it@cs.unibo.it \
--cc=erlang-questions@erlang.org \
--cc=formal-methods@cs.uidaho.edu \
--cc=forum@jsoftware.com \
--cc=generic-haskell@generic-haskell.org \
--cc=grin@di.unipi.it \
--cc=gulp@di.unipi.it \
--cc=ipalist@win.tue.nl \
--cc=lics@research.bell-labs.com \
--cc=logic@CS.Cornell.EDU \
--cc=logic@theory.lcs.mit.edu \
--cc=lprolog@cis.upenn.edu \
--cc=lprolog@cs.umn.edu \
--cc=mercury-users@cs.mu.OZ.AU \
--cc=mlnet@swi.psy.uva.nl \
--cc=pl-seminar@ccs.neu.edu \
--cc=plt-scheme@fast.cs.utah.edu \
--cc=prolog-vendors@sics.se \
--cc=relmics-list@heraklit.informatik.unibw-muenchen.de \
--cc=rewriting@ens-lyon.fr \
--cc=sicstus-users@sics.se \
--cc=skeletons@dcs.ed.ac.uk \
--cc=theorem-provers@ai.mit.edu \
--cc=theorynt@listserv.nodak.edu \
--cc=users@mozart-oz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox