Hiyas,
$ ghc -O -fvia-C -O2-for-C -Wall -package lang -prof -auto -c -o Tokens.o Tokens.lhs
$ ghc -O -fvia-C -O2-for-C -Wall -package lang -prof -auto -c -o IA.o IA.lhs
ghc-5.00.2: panic! (the `impossible' happened, GHC version 5.00.2):
Oversize heap check detected. Please try
On Sun, Sep 30, 2001 at 03:29:44PM +0100, Ian Lynagh wrote:
$ ghc -O -fvia-C -O2-for-C -Wall -package lang -prof -auto -c -o Tokens.o Tokens.lhs
$ ghc -O -fvia-C -O2-for-C -Wall -package lang -prof -auto -c -o IA.o IA.lhs
ghc-5.00.2: panic! (the `impossible' happened, GHC version 5.00.2):
Has anyone ever tried to pass/receive a float to/from a Java app? If so, how did you
manage it?
I need an algorithm for converting an IEEE 754 format float to a 32 bit integer?
I want something that can convert a haskell float into a int that can be stored to
disk for later input to a Java
Hamilton Richards [EMAIL PROTECTED] writes:
At 12:20 PM -0500 9/29/01, Colin Paul Adams wrote:
I have just been reading through the Haskell report to refresh my
memory of the language. I was surprised to see this:
The character type Char is an enumeration and consists of 16 bit values,
Jens == Jens Petersen [EMAIL PROTECTED] writes:
Jens 16 bits is enough to describe the Basic Multilingual Plane
Jens and I think 24 bits all the currently defined extended
Jens planes. So I guess the report just refers to the BMP.
I guess it does, and I think back in 1998 that may
30 Sep 2001 22:28:52 +0900, Jens Petersen [EMAIL PROTECTED] pisze:
16 bits is enough to describe the Basic Multilingual Plane
and I think 24 bits all the currently defined extended
planes. So I guess the report just refers to the BMP.
In early days the Unicode Consortium was doing
30 Sep 2001 14:43:21 +0100, Colin Paul Adams [EMAIL PROTECTED] pisze:
I think it should either be amended to mention the BMP subset of
Unicode, or, better, change the reference from 16-bit to 24-bit.
24-bit is not accurate. The range from 0 to 0x10 has
20.087462841250343 bits. There is no
sorry for the me too post, but this has been a major pet peeve of mine
for a long time. 16 bit unicode should be gotten rid of, being the worst
of both worlds, non backwards compatable with ascii, endianness issues
and no constant length encoding utf8 externally and utf32 when
worknig with
Hi all
The report says The layout rule matches only those open braces that it
has inserted in the lexical structure section. However, in the syntax
section function L starts
L (t:ts) (m:ms) = } : (L (t:ts) ms) if parse-error(t) (Note 1)
which AFAICT will implicitly close an explicit open
At 2001-09-30 00:37, [EMAIL PROTECTED] wrote:
Has anyone ever tried to pass/receive a float to/from a Java app? If so,
how did you manage it?
Using JNI through Haskell's FFI. Both define their floats and doubles as
C 'float' and 'double', so I don't bother with any conversion. I haven't
At 2001-09-30 07:29, Marcin 'Qrczak' Kowalczyk wrote:
Some time ago the Unicode Consortium slowly began switching to the
point of view that abstract characters are denoted by numbers in the
range U+..10.
It's worth mentioning that these are 'codepoints', not 'characters'.
Sometimes a
Colin Paul Adams [EMAIL PROTECTED] writes:
Jens == Jens Petersen [EMAIL PROTECTED] writes:
Jens 16 bits is enough to describe the Basic Multilingual Plane
Jens and I think 24 bits all the currently defined extended
Jens planes. So I guess the report just refers to the BMP.
12 matches
Mail list logo
