From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: FP/IP and performance (in general) and Patterns... (Re: [Caml-list] Avoiding shared data)
Date: Wed, 5 Oct 2005 15:45:52 +0200 [thread overview]
Message-ID: <20051005134552.GA1042@first.in-berlin.de> (raw)
On Tue, Oct 04, 2005 at 07:45:12PM -0500, Brian Hurt wrote:
[...]
> The big advantage of FP programming IMHO is not performance, but instead
> *correctness*. With today's multi-gigahertz machines with multi-gigabytes
> of memory, performance isn't as critical as it used to be. But
> correctness- especially automatically gaurenteed correctness on projects
> spanning hundreds of thousands of lines of code and dozens of developers
> maintained over decades of time- starts becoming critical.
Yes, I agree on this.
I get daily messages from an buglist-mailinglist, where most often
things like typical memory-exploits are the reason of why a system
or a process can be exploited.
So, the typical "out of bounds" and "format string" problems
are typical security risks.
(Btw: is OCaml's format-string stuff from the Printf-module save in
this respect?!)
> I'd quite
> happily trade off 10% performance for correctness, or even 50%
> performance.
Well, if the code with correctness is nearly as fast as the code without,
it would be best.
>
> FP is a huge gain in correctness, because it allows me to *control
> mutability*. If I pass a mutable data structure to a block of code there
> is an instant implicit contract between the caller and the callee on how
> (or wether) to modify the mutable data structure. It doesn't matter what
> the contract is- wether it's to not modify the structure at all, to allow
> optional modification (either unlimited or only in certain ways), or to
> require certain modifications- a dependency between the two different
> peices of code exists. And this dependency, this contract, is probably
> undocumented and always unchecked by the compiler, which means it's a
> maintaince nightmare waiting to happen. One peice of code gets modified
> to violate the contract, perhaps even unknowingly, or perhaps due to some
> changing requirement, and untouched code thousands of lines away suddenly
> breaks.
Yes, this is a very well description of the FP-advantages.
Nevertheless, if a solution is too slow, it hinders
people from adopting FPLs for their programmig, and
software remains unsecure/unsafe, because they again and again
will choose the unsafe langauges... :(
Ciao,
Oliver
next reply other threads:[~2005-10-05 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 13:45 Oliver Bandel [this message]
2005-10-05 23:20 ` William Lovas
-- strict thread matches above, loose matches on Subject: below --
2005-10-03 20:03 Ant: Re: Ant: Re: Ant: Re: [Caml-list] Avoiding shared data Martin Chabr
2005-10-04 2:53 ` skaller
2005-10-04 16:15 ` Brian Hurt
2005-10-04 16:47 ` FP/IP and performance (in general) and Patterns... (Re: [Caml-list] Avoiding shared data) Oliver Bandel
2005-10-04 22:38 ` Michael Wohlwend
2005-10-05 0:31 ` Jon Harrop
2005-10-04 22:39 ` Christopher A. Watford
2005-10-04 23:14 ` Jon Harrop
2005-10-05 12:10 ` Oliver Bandel
2005-10-05 13:08 ` Jon Harrop
2005-10-05 15:28 ` skaller
2005-10-05 0:45 ` Brian Hurt
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=20051005134552.GA1042@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--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;
as well as URLs for NNTP newsgroup(s).