A programmer who hasn't been exposed to all four of the imperative, functional, objective, and logical programming styles has one or more conceptual blindspots. It's like knowing how to boil but not fry. Programming is not a skill one develops in five easy lessons.
-- Tom Christiansen
I'd like to spend some of my time to learn functional programming languages.
I don't think I'll write an entire application in Lisp or Scheme; I'm more
interested in the "enlightenment experience" that functional programming languages
bring. In other terms, I think I'll design and write code better, after studying
some principles of functional programming. A good example of what I mean is the
Schwartzian Transform. merlyn said (I can't remember where I've read it) that
he wrote it quite naturally, simply (if the word 'simply' is correct) because he
was trained to think, let's say, functionally :)
So far so good. I know that the topic of functional programming has been treated
in the Monastery in the past. So I ask your help to build a book about
Perl and Functional Programming (the title is not so restrictive)
using the material that is available in the Monastery so far, in the sense
I've described here (Lack of structure. Channeling structure).
So this node is under construction.
First of all, I provide links to the nodes I've collected so far, waiting for
you comments about How to give a structure to them and How to add value to them.
- A Lisp interpreter written in Perl
- More Lisp-In-Perl
- Lisp Rocks
- Lisp is More Evaluatable
- Lisp vs. Perl Round 3: Operator Associativity and Manipulation
- Functional Perl as Scheme and functional XML parsing
- Why I like functional programming
- infinite series
- A Perl implementation of the concepts of stream and delayed evaluation, using tied arrays
- Schwartzian Transform
- Re: Functional perl please
- Computing the Hamming Sequence Functionally
- mapcar -- map for more than one list
Links outside Perlmonks
11/2/2001 Update: Added "Outside Links" Section. Added quote from Tom Christiansen. Added some descriptions.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||