-- Forwarded message --
From: Alberto G. Corona agocor...@gmail.com
Date: 2008/12/19
Subject: Re: Fwd: [Haskell-cafe] Haskell as a religion
To: Dan Piponi dpip...@gmail.com
As far as I know, const only protect from updates that the compiler can
detect at compilation time
But many features need other features. For example, the option to use
referential transparency will be common in future languages for multicore
programming purposes. This creates the problem of separating
side-effect-free code from side-effect code. For this purpose, a strong type
system at
Alberto G. Corona schrieb:
But many features need other features. For example, the option to use
referential transparency will be common in future languages for
multicore programming purposes. This creates the problem of separating
side-effect-free code from side-effect code.
In C/C++
On Thu, Dec 18, 2008 at 4:15 PM, Henning Thielemann
schlepp...@henning-thielemann.de wrote:
Extrapolating the habit of programmers from the past to the future, I
predict that Haskell can only become a mainstream language once there is
a cleaner, simpler, safer and more powerful programming
Henning Thielemann wrote:
Alberto G. Corona schrieb:
But many features need other features. For example, the option to use
referential transparency will be common in future languages for
multicore programming purposes. This creates the problem of separating
side-effect-free code from
On Thu, Dec 18, 2008 at 4:15 PM, Henning Thielemann
schlepp...@henning-thielemann.de wrote:
In C/C++ referential transparent functions code can be declared by
appending a 'const' to the prototype, right?
For one thing, some fields in a const C++ object can be explicitly set
mutable. mutable is
