From: Eray Ozkural <exa@kablonet.com.tr>
To: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ANNOUNCE: mod_caml 1.0.6 - includes security patch
Date: Tue, 20 Jan 2004 14:30:35 +0200 [thread overview]
Message-ID: <200401201430.35033.exa@kablonet.com.tr> (raw)
In-Reply-To: <20040120113108.GB13600@fichte.ai.univie.ac.at>
On Tuesday 20 January 2004 13:31, Markus Mottl wrote:
> "where" is one keyword, which I might find useful. Code can be made much
> more readable if function applications come first and values used in it
> are defined further below. Otherwise, the user may have to scan large
> portions of value definitions before getting to the "core" of a function.
Absolutely! It looks much better than 5 nested let scopes (although they are
semantically identical). Where was this inefficient DFT function I had
written. Ah, here it is:
dft :: (RealFloat a) => (SampleVector (Complex a)) -> Int
-> (SampleVector (Complex a))
dft x n =
listArray (0, (n-1)) [transform f | f <- [0..(n-1)]]
where
transform f = scale * (foldl1 (+) [freqcomp f k | k <- [0..(n-1)]])
freqcomp f k = (x!k) * (exp_polar (-(2 * (fromIntegral k)
* pi * (fromIntegral f) ) /
(fromIntegral n)) )
scale = 1/(fromIntegral n)
I find use of where keyword much more readable in many places.
Cheers,
--
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara KDE Project: http://www.kde.org
www: http://www.cs.bilkent.edu.tr/~erayo Malfunction: http://mp3.com/ariza
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-------------------
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:[~2004-01-20 12:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 14:03 Richard Jones
[not found] ` <4006AC01.F2AD2741@decis.be>
2004-01-15 15:42 ` Richard Jones
2004-01-15 16:19 ` Markus Mottl
2004-01-15 16:53 ` Richard Jones
2004-01-16 6:15 ` james woodyatt
2004-01-16 9:34 ` Richard Jones
2004-01-16 19:05 ` Brian Hurt
2004-01-16 18:52 ` Yutaka OIWA
2004-01-16 19:20 ` Markus Mottl
2004-01-16 19:01 ` Markus Mottl
2004-01-19 10:13 ` Luc Maranget
2004-01-19 11:36 ` Richard Jones
2004-01-19 14:43 ` Luc Maranget
2004-01-19 16:10 ` Richard Jones
2004-01-19 17:46 ` Markus Mottl
2004-01-19 18:05 ` Richard Jones
2004-01-19 21:45 ` Eray Ozkural
2004-01-20 11:31 ` Markus Mottl
2004-01-20 12:30 ` Eray Ozkural [this message]
2004-01-21 14:01 ` skaller
2004-01-20 17:34 ` Michal Moskal
2004-01-20 17:52 ` Eray Ozkural
2004-01-20 18:54 ` Michal Moskal
2004-01-20 19:21 ` Markus Mottl
2004-01-20 19:37 ` David Brown
2004-01-20 20:38 ` Eray Ozkural
2004-01-21 19:07 ` Max Kirillov
[not found] ` <Pine.GSO.4.53.0401211150520.10508@cascade.cs.ubc.ca>
2004-01-22 2:15 ` Max Kirillov
2004-01-20 23:00 ` Brian Hurt
2004-01-20 23:48 ` Eray Ozkural
2004-01-21 0:34 ` David Brown
2004-01-21 2:32 ` Eray Ozkural
2004-01-21 2:34 ` Eray Ozkural
2004-01-21 2:34 ` Shawn Wagner
2004-01-21 9:43 ` Andreas Rossberg
2004-01-21 5:16 ` Brian Hurt
2004-01-19 21:59 ` Kenneth Knowles
2004-01-19 18:18 ` David Brown
2004-01-19 19:15 ` Markus Mottl
2004-01-19 19:19 ` David Brown
[not found] ` <20040119185746.A12690@beaune.inria.fr>
2004-01-19 18:07 ` Richard Jones
2004-01-20 1:29 ` 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=200401201430.35033.exa@kablonet.com.tr \
--to=exa@kablonet.com.tr \
--cc=caml-list@inria.fr \
--cc=erayo@cs.bilkent.edu.tr \
/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).