On Thu, 27 Dec 2007 14:37:51 +0200, Yitzchak Gale <[EMAIL PROTECTED]> wrote:
I wrote:
Like any type, only certain operations make
sense on functions...
Yes, but one can store the result of an operation to disk except in
the
particular case the result happen to be a function.
No, you can only store the result of an operation to
disk in the particular case that the result type represents
a list of bytes. Otherwise, you have to serialize it first...
But it is not clear at all how you could define a general
serialization method for functions.
Isn't that confusing levels of abstractions ?
Of course functions are bytes, 'cause they are already stored as bytes
in
RAM.
That is just the point. A function in Haskell is an abstraction,
not bytes in RAM.
The compiler might implement the same function in several places,
with different bytes in each place. Or it might decide to combine it
into other functions, and not store any bytes in RAM at all for this
function.
The function itself represents a way of doing a calculation. It is not an
object that can do the calculation.
I think you try to say that the time cannot be stored.
________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Servers.
part000.txt - is OK
http://www.eset.com
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
