From: Bulat Ziganshin [mailto:[EMAIL PROTECTED]
and one more question: is it possible to download sources of http
server mentioned in this article? i want to browse the code, it's no
matter how it compiles and works
I believe the web-server mentioned became HWS:
Hello Alistair,
Friday, May 20, 2005, 11:18:15 AM, you wrote:
BA I believe the web-server mentioned became HWS:
BA http://cvs.sf.net/viewcvs.py/haskell-libs/libs/hws-wp/hws-wp/src/
thank you
BA (I don't see any error/inconsistency in the two quotes; they just seem to be
BA talking about
Bulat,
just for the record, it's not my article. Although I have the
privilege of sharing a somewhat similar name with the geniuses
around here, I didn't have any part in that text. ;-)
You were wondering about this declaration:
foreign import ccall unsafe sin :: Float - Float
I guess you
On Fri, 2005-05-20 at 11:30 +0200, Peter Simons wrote:
Since pure FFI calls don't have any side-effects, they are
always safe to be called unsafely. (Yes, the choice of the
words safe and unsafe is a bit unfortunate in the standard
here.)
To try and undo this confusion we need to recall what
Duncan Coutts writes:
So to sumarise the pairings:
* you _must_ make a safe call to an unsafe foreign function
* you _may_ make an unsafe call to a safe foreign function
It's a contravariance :-)
I'd use a slightly different term. Declaring a function that
needs special
Hello Peter,
Friday, May 20, 2005, 1:30:08 PM, you wrote:
PS just for the record, it's not my article. Although I have the
PS privilege of sharing a somewhat similar name with the geniuses
PS around here, I didn't have any part in that text. ;-)
i answered your letter but wrote to Simon PJ
PS
Bulat Ziganshin writes:
PS Since pure FFI calls don't have any side-effects, they are
PS always safe to be called unsafely.
sorry, but even pure C function can call back to Haskell world and
lead to GC.
Um, right. I said I didn't understand these things
completely either. Guess I was
Hi,
the following (reduced) example used to go through with ghc-6.2.2 but
fails with ghc-6.4. Which behaviour is correct? I compile with:
ghc -fglasgow-exts Context.hs
module Context where
class Language a
class Language a = Logic a b | a - b
class (Language a, Logic b c, Logic d e)
=
Would it be possible to extend the DEPRECATED pragma to
allow one to deprecate an instance of a class?
I was thinking about the recent discussion of APIs on
haskell-cafe, where Jérémy Bobbio complained about using
Booleans as arguments to libaray functions, preferring
instead sensibly named data
