From: "Marcin 'Qrczak' Kowalczyk" <qrczak@knm.org.pl>
To: caml-list@inria.fr
Subject: RE: [Caml-list] variant with tuple arg in pattern match?
Date: Tue, 10 Apr 2001 15:12:11 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0104101501270.27758-100000@zodiac.mimuw.edu.pl> (raw)
In-Reply-To: <DD7356599083414BA450E3DCC4119B8B06C435@NT.kal.com>
On Tue, 10 Apr 2001, Dave Berry wrote:
> You certainly can avoid currying in functional languages. Currying is a
> hack that was created to keep the lambda calculus as simple as possible.
It's not a hack. When functions can return functions, there is no need of
inventing the concept of multiparameter functions.
> 1. Multiple arguments. Fine for the calculus, but in any language with
> tuples or records we can just write f(x,y), like everybody else.
This is as much of a hack as currying. Why to pack arguments in a tuple
when you could simply use currying?
> In cases where a function is explicitly returning another (as opposed to
> just simulating multiple arguments), I think the explicit binding
> describes what is happening more clearly.
It's not opposition. This is semantically the same, so there is no need of
introducing a syntactic difference.
Does map take a function and a list, returning a list, or does it lift
a function to a function operating on a list? There is no difference.
--
Marcin 'Qrczak' Kowalczyk
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-04-10 13:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 12:17 Dave Berry
2001-04-10 13:12 ` Marcin 'Qrczak' Kowalczyk [this message]
2001-04-10 21:26 ` Bruce Hoult
2001-04-10 22:34 ` John Prevost
2001-04-10 13:51 ` Frank Atanassow
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 17:33 Dave Berry
2001-04-10 22:34 ` John Prevost
2001-04-10 17:25 Dave Berry
2001-04-10 23:16 ` Marcin 'Qrczak' Kowalczyk
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=Pine.LNX.4.21.0104101501270.27758-100000@zodiac.mimuw.edu.pl \
--to=qrczak@knm.org.pl \
--cc=caml-list@inria.fr \
/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