I think you're asking whether POSIX types should
be given a type/synonym on the Haskell side. The
Posix library does define some of them, but not
all - e.g., size_t isn't.
I'm sure patches which extended that library so as
to have these would be welcomed by the GHC developers.
--sigbjorn
Simon Marlow [EMAIL PROTECTED] writes:
Sergey:
One small correction:
The sed script should be:
sed -e 's/.*\/\([^\/][^\/]*\)\.hs/$(E)\/\1.o, $(E)\/\1.hi/'
Of course:
:g/.*\/\([^\/][^\/]*\)\.hs/s//$(E)\/\1.o, $(E)\/\1.hi/
in vi should also work.
-odir blah
IIRC, this has already been discussed quickly some time ago, but
anyway: To conform more with the rest of the *nix world and decrease
the confusion of my students, I'd like GHC to be less verbose by
default. IMHO the following messages should not be issued without
any commandline flags:
ghc:
[EMAIL PROTECTED] (Martin Erwig) wrote,
I am wondering what is the best way (in terms of
easy-to-use and easy-to-install) to use a parser
for Haskell in Hugs. As far as I know the parsers
by Sven Panne and Manuel Chakravarty require ghc.
I didn't write a parser for parsing Haskell - I only
Hello,
I come up again with a topic I mentioned some years ago.
I would like to have a comparison instruction that compares the internal
reference of two objects.
Let's call it "req".
req :: a - a - Bool
-- of course it is an equivalence operation
req x x = True
req x y = req y x
(req x
The expression
let x=[1..] in x==x
would not terminate in the first case but succeed in the second.
But, much worse
let x = (a,b) in x `req` x = True
but
(a,b) `req` (a,b) = False
So referential transparency is lost. This is a high price to
Simon Marlow wrote:
[EMAIL PROTECTED] (Martin Erwig) wrote,
I am wondering what is the best way (in terms of easy-to-use and
easy-to-install) to use a parser for Haskell in Hugs. [...]
Our Haskell parser library works fine with Hugs: [...] It's not quite
complete (it doesn't do fixity
let x=[1..] in x==x
would not terminate in the first case but succeed in the second.
But, much worse
let x = (a,b) in x `req` x = True
but
(a,b) `req` (a,b) = False
So referential transparency is lost. This is a high price to pay.
You are
"Martin" == Martin Erwig [EMAIL PROTECTED] writes:
Martin I am wondering what is the best way (in terms of
Martin easy-to-use and easy-to-install) to use a parser
Martin for Haskell in Hugs. As far as I know the parsers
Martin by Sven Panne and Manuel Chakravarty require ghc.
There is also
I would like to have a comparison instruction that compares
the internal
reference of two objects.
Let's call it "req".
req :: a - a - Bool
By coincidence, I was just looking at GHC's documentation on
stable names
and pointers, and it seems relevant here.
I would like to have a comparison instruction that compares the internal
reference of two objects.
Let's call it "req".
req :: a - a - Bool
By coincidence, I was just looking at GHC's documentation on stable names
and pointers, and it seems relevant here.
Andreas C. Doering wrote:
| I would like to have a comparison instruction that compares the internal
| reference of two objects.
It might be of interest here to talk about a paper that Dave Sands and I
have recently submitted to a conference, about something we call
"observable sharing".
It
"D. Tweed" wrote:
On Tue, 27 Jul 1999, Simon Marlow wrote:
req a b = unsafePerformIO $ do
a' - makeStableName a
b' - makeStableName b
return (a' == b')
That's exactly what to use in a situation like this. Pointer equality loses
referential transparency in general (as
On Tue, 27 Jul 1999, Andreas C. Doering wrote:
let x=[1..] in x==x
would not terminate in the first case but succeed in the second.
But, much worse
let x = (a,b) in x `req` x = True
but
(a,b) `req` (a,b) = False
So referential
On 27-Jul-1999, Ralf Muschall [EMAIL PROTECTED] wrote:
Lennart Augustsson wrote:
b) Haskell does not have a function called primShiftInt so
you can't say that's intended or not intended.
I looked once more where it appears: It is used in the
extension libraries which come with hugs
On Tue, 27 Jul 1999, Simon Marlow wrote:
req a b = unsafePerformIO $ do
a' - makeStableName a
b' - makeStableName b
return (a' == b')
That's exactly what to use in a situation like this. Pointer equality loses
referential transparency in general (as Simon P.J. pointed out),
16 matches
Mail list logo
