From: Siegfried Gonzi <siegfried.gonzi@stud.uni-graz.at>
To: Noel Welsh <noelwelsh@yahoo.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Easy solution in OCaml?
Date: Mon, 28 Apr 2003 14:05:16 +0200 [thread overview]
Message-ID: <3EAD18FC.7050108@stud.uni-graz.at> (raw)
In-Reply-To: <20030427164326.34082.qmail@web41211.mail.yahoo.com>
Noel Welsh wrote:
>Let me just check - you don't consider Scheme to be a
>functional language?
>
I think the following nails it down:
==
Historically, Lisp was one of the first languages to accomodate a
functional programming style, and for this reason, some people still
call it a functional programming language. However, that's not correct
in a strict sense. Several paths have been followed since then, and
while languages like Miranda and Haskell were surely influenced by early
Lisp dialects, they have taken a purely functional approach. Today's
Lisp dialects, foremostly Common Lisp, don't see any problems in making
use of side effects, using iteration instead of recursion, using
object-oriented abstraction if useful for the problem at hand, and so
on. Just use the best abstraction for your current problem.
==
The above quote was pinched up from comp.lang.lisp; they had there
discussions the other day. Okay, Scheme is considerd even more
"functional" than Lisp, but the above quote is, I think, valid for
Scheme too.
Monads are not mentioned in the above quote, but I would like to stress
that Clean circumvents monadic file input-output but ensures a
functional style with no side effects! I think they were the first to
success in this way.
>
>Just about any alternative syntax would be cleaner
>than O'Caml! ;-)
>
>Noel, Scheme hacker and O'Caml lurker
>
One thing which I would like to have solved for myself:
Will my Scheme code be readable a year later ? Or would in such a case
Clean or OCaml pay off?
S. Gonzi
-------------------
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 parent reply other threads:[~2003-04-28 13:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030427164326.34082.qmail@web41211.mail.yahoo.com>
2003-04-28 12:05 ` Siegfried Gonzi [this message]
2003-04-28 13:54 ` Noel Welsh
2003-04-28 14:22 ` David Brown
2003-04-28 14:38 ` sebastien FURIC
2003-04-28 18:14 ` Eray Ozkural
2003-05-03 14:37 ` John Max Skaller
2003-05-03 16:57 ` Eray Ozkural
2003-04-28 15:27 isaac gouy
2003-04-28 16:38 ` brogoff
2003-04-28 17:13 ` isaac gouy
2003-04-28 17:48 ` Brian Hurt
2003-04-28 17:50 ` brogoff
2003-04-28 18:31 ` Eray Ozkural
2003-04-29 6:46 ` Siegfried Gonzi
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 6:05 Siegfried Gonzi
2003-04-25 8:19 ` sebastien FURIC
2003-04-25 15:46 ` Brian Hurt
2003-04-25 16:34 ` Ville-Pertti Keinonen
2003-04-26 13:45 ` Siegfried Gonzi
2003-04-26 21:51 ` Brian Hurt
2003-04-27 15:01 ` Siegfried Gonzi
2003-04-28 15:43 ` Brian Hurt
2003-04-29 5:46 ` John Max Skaller
2003-04-25 16:59 ` Markus Mottl
2003-04-26 6:25 ` Siegfried Gonzi
2003-04-27 14:13 ` Siegfried Gonzi
2003-04-27 16:54 ` Eray Ozkural
2003-04-28 5:00 ` Siegfried Gonzi
2003-04-28 17:45 ` malc
2003-04-28 18:16 ` Shivkumar Chandrasekaran
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=3EAD18FC.7050108@stud.uni-graz.at \
--to=siegfried.gonzi@stud.uni-graz.at \
--cc=caml-list@inria.fr \
--cc=noelwelsh@yahoo.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