From: oliver@first.in-berlin.de (Oliver Bandel)
To: caml-list@inria.fr
Cc: ocaml_beginners@yahoogroups.com
Subject: [Caml-list] Books on FPL
Date: Sun, 16 Mar 2003 10:24:49 +0100 [thread overview]
Message-ID: <20030316092449.GA560@first.in-berlin.de> (raw)
Hello,
this night I have looked for papers on tail-recursion.
I found some interesting papers. But I also found
books on FP-programming, which are highly interesting
and available in web.
# Recursion, Iteration
# and
# Functional Languages:
http://www.cs.trinity.edu/~jhowland/ccsc98/ccsc98/ccsc98.html
This author also has written texts about selecting languages
in computer science education, and other interesting texts too.
# Computer Science:
# Abstraction to Implementation
http://www.cs.hmc.edu/claremont/keller/webBook/index.htm
Contains a Chapter on High-Level- and one one Low-Level-
Functional Programming (Chap. 3 and Chap. 4).
Covers Object-Oriented programming as well.
# LISP Primer:
http://grimpeur.tamu.edu/~colin/lp/
I have found other interesting material on tail-recursion,
but did not add all these here. If the explanations in the
above-books are not enough, ask me (or google).
But one paper on tail-recursion (forgotten the URL, but the
filename is: "primitive-slides.pdf") I can recommend:
John Cowles, Consistelntly Adding Primitive Recursive
Functions in ACL2
Explains tail-recursion in a more abstratced way, but does
use abstracted formalisms: does not leave the programmers
perspective and therefore is a very good attempt to
do it abstract as well as grounded :)
That's, what I like, and how programmers can learn new
stuff, even if they are not researchers.
(When formalisms are introduced more gently (maybe two-column
page layout and on one column using this style of "concrete abstraction"
and on the other column using formalisms, then you can gain
more understanding in your readers... so, the mentioned paper can be
seen as using an "example" as a specification/explanation of a concept.
This is a very good attempt! Because functional languages are
often explained as "executable" specifications, why not using
this advantage of FPLs to explain the programming concepts? (...) ))
Ciao,
Oliver
P.S.: It seems to me, that my style of writing texts should be a hint
to start Lisp-Programming. ;-)
-------------------
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
next reply other threads:[~2003-03-16 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 9:24 Oliver Bandel [this message]
2003-03-16 14:22 ` Oliver Bandel
2003-03-17 2:44 ` Sergey Goldgaber
-- strict thread matches above, loose matches on Subject: below --
2003-03-16 9:24 Oliver Bandel
2003-05-09 13:52 ` Florian Hars
2003-05-09 14:55 ` Oliver Bandel
2003-05-11 11:49 ` Nicolas Cannasse
2003-05-13 7:51 ` Florian Hars
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=20030316092449.GA560@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
--cc=ocaml_beginners@yahoogroups.com \
/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