From: "Dave Berry" <Dave@kal.com>
To: "Frank Atanassow" <franka@cs.uu.nl>
Cc: "Daniel de Rauglaudre" <daniel.de_rauglaudre@inria.fr>,
<caml-list@inria.fr>
Subject: RE: [Caml-list] variant with tuple arg in pattern match?
Date: Tue, 10 Apr 2001 18:33:09 +0100 [thread overview]
Message-ID: <DD7356599083414BA450E3DCC4119B8B06C4E4@NT.kal.com> (raw)
> From: Frank Atanassow [mailto:franka@cs.uu.nl]
> Sent: Tuesday, April 10, 2001 14:51
>
> When you say "currying" you are talking about a syntactic
> matter which arises
> due to positional application. When Daniel said that "currying" is
> basic to the lambda-calculus, he was talking about a more fundamental,
> semantic matter.
Daniel did not write the sentence you attribute to him. He said that
currying is basic to functional programming. There are many differences
between functional programming and the pure lambda calculus. Consider:
let-abstraction, the value polymorphism rule, restrictive type systems,
syntax, tuples, records, exceptions, assignment, modules, IO, size of
programs, etc.
As for syntax versus semantics, I nearly wrote "semantic hack", until I
realised that it only works if the syntax also supports it.
> If you look at lambda-calculus from a sufficiently abstract
> perspective where
> the syntax is immaterial,...
... then you're not talking about functional programming.
> And how do you define g in the first case if you don't have
> semantical currying?
Possibly there is some terminological confusion here. I've only ever
seen "currying" used to mean the encoding of multiple arguments using
higher order functions. I certainly do not oppose the use of
higher-order functions for other uses, and of course this requires the
building of closures as you describe.
Dave.
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next reply other threads:[~2001-04-10 17:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 17:33 Dave Berry [this message]
2001-04-10 22:34 ` John Prevost
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 17:25 Dave Berry
2001-04-10 23:16 ` Marcin 'Qrczak' Kowalczyk
2001-04-10 12:17 Dave Berry
2001-04-10 13:12 ` Marcin 'Qrczak' Kowalczyk
2001-04-10 21:26 ` Bruce Hoult
2001-04-10 22:34 ` John Prevost
2001-04-10 13:51 ` Frank Atanassow
2001-04-08 0:22 jgm
2001-04-04 11:04 Chris Hecker
2001-04-04 18:47 ` Alain Frisch
2001-04-04 19:18 ` Patrick M Doane
2001-04-04 19:36 ` Chris Hecker
2001-04-04 19:49 ` Daniel de Rauglaudre
2001-04-05 8:19 ` Christian RINDERKNECHT
2001-04-04 19:49 ` Patrick M Doane
2001-04-06 13:52 ` Xavier Leroy
2001-04-07 1:42 ` Patrick M Doane
2001-04-07 6:44 ` Daniel de Rauglaudre
2001-04-07 7:42 ` Fergus Henderson
2001-04-08 19:45 ` Pierre Weis
2001-04-08 20:37 ` Charles Martin
2001-04-08 23:57 ` Brian Rogoff
2001-04-09 0:22 ` Alain Frisch
2001-04-09 16:07 ` Pierre Weis
2001-04-10 8:23 ` Michel Mauny
2001-04-10 9:14 ` Xavier Leroy
2001-04-10 10:09 ` Michel Mauny
2001-04-10 10:44 ` reig
2001-04-10 11:32 ` Michel Mauny
2001-04-10 11:47 ` reig
2001-04-10 12:10 ` reig
2001-04-10 12:35 ` Michel Mauny
2001-04-10 12:49 ` Marcin 'Qrczak' Kowalczyk
2001-04-09 6:23 ` Mattias Waldau
2001-04-09 7:34 ` Daniel de Rauglaudre
2001-04-09 15:57 ` Pierre Weis
2001-04-10 9:07 ` Sven LUTHER
2001-04-09 8:20 ` Christian RINDERKNECHT
2001-04-10 2:54 ` Patrick M Doane
2001-04-10 19:04 ` John Max Skaller
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=DD7356599083414BA450E3DCC4119B8B06C4E4@NT.kal.com \
--to=dave@kal.com \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@inria.fr \
--cc=franka@cs.uu.nl \
/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;
as well as URLs for NNTP newsgroup(s).