Sorry for interruption, but I feel this thread of discussion
includes four different aspects of `binary' data:
1. Reading and writing binary data in a prescribed format.
Typical examples are image data in GIF, TIFF, Sun Raster etc,
and user-account statistics files used in Unix.
>This thread and particularly the following passage:
>
> "If I understand this right, you're suggesting essentially dumping
>out part of the Haskell heap to a file."
>
>reminds me very strongly of APL, where dumping the current state of
>the system into a binary file that you can later reloa
"Steve" == Steve Roggenkamp <[EMAIL PROTECTED]> writes:
Steve> I would like to use Haskell for several larger scale
Steve> projects, but I can't figure out how to read and write
Steve> binary data. It does not appear that the language supports
Steve> binary files. Am I missing something
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Tony Davie wrote:
> This has well know disadvantages. Simon has already pointed out that
> it's not relocatable.
How is it done in APL and in other systems that do it (SmallTalk
and some LISP systems, according to another p
> I would like to use Haskell for several larger scale projects, but I
> can't figure out how to read and write binary data. It does not appear
> that the language supports binary files. Am I missing something?
Colin Runciman and his Merrie Men are working on writing
Haskell values into binary
--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
This thread and particularly the following passage:
"If I understand this right, you're suggesting essentially dumping
out part of the Haskell heap to a file."
reminds me very strongly of APL, where dumping the current
