From: "sebastien FURIC" <sebastien.furic@tni-valiosys.com>
To: David Brown <caml-list@davidb.org>
Cc: Siegfried Gonzi <siegfried.gonzi@stud.uni-graz.at>,
Noel Welsh <noelwelsh@yahoo.com>,
caml-list@inria.fr
Subject: Re: [Caml-list] Easy solution in OCaml?
Date: Mon, 28 Apr 2003 16:38:07 +0200 [thread overview]
Message-ID: <3EAD3CCF.C412B078@tni.fr> (raw)
In-Reply-To: <20030428142223.GA3924@opus.davidb.org>
David Brown a écrit :
>
> On Mon, Apr 28, 2003 at 02:05:16PM +0200, Siegfried Gonzi wrote:
>
> > 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.
>
> So having feature in addition to functional features disqualifies a
> language from being labelled. All of the accusations given certainly
> apply to Ocaml as well. Having objects and side-effects doesn't seem to
> stop me from doing functional programming.
>
> To me, the core feature of functional programming are first class
> closures. Everything else just makes it more convenient.
So Smalltalk is a functional language ;-)
Maybe tail call optimisation has to be considered as a necessary
feature for a langage to qualify ?
>
> Why someone would think using the best abstraction for your current
> problem is a bad thing is beyond me. I think that is one of the
> strengths of Ocaml, is that it can accomodate this so well.
Agreed.
Cheers,
Sébastien
-------------------
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 prev parent reply other threads:[~2003-04-28 14:43 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
2003-04-28 13:54 ` Noel Welsh
2003-04-28 14:22 ` David Brown
2003-04-28 14:38 ` sebastien FURIC [this message]
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=3EAD3CCF.C412B078@tni.fr \
--to=sebastien.furic@tni-valiosys.com \
--cc=caml-list@davidb.org \
--cc=caml-list@inria.fr \
--cc=noelwelsh@yahoo.com \
--cc=siegfried.gonzi@stud.uni-graz.at \
/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