Hello,
I have a question about the semantics of finalizers of ForeignPtrs:
If an in scope value has a reference to a ForeignPtr is the foreign
object always kept alive, even if that reference is not used? Or do I
always need to wrap each computation, which needs to have the foreign
object alive,
Hi,
Am Sonntag, den 19.06.2011, 15:33 +1000 schrieb Mark Wright:
Fedora, Debian, FreeBSD:
I don't use them, however I think they have very good support for
Haskell packaging. For example, Fedora updates the haddock documentation
index as pkgs are installed and removed
same on Debian,
On 19 June 2011 20:26, Joachim Breitner nome...@debian.org wrote:
Hi,
Am Sonntag, den 19.06.2011, 15:33 +1000 schrieb Mark Wright:
Fedora, Debian, FreeBSD:
I don't use them, however I think they have very good support for
Haskell packaging. For example, Fedora updates the haddock
Hi,
Am Sonntag, den 19.06.2011, 20:31 +1000 schrieb Ivan Lazar Miljenovic:
same on Debian, file:///usr/share/doc/ghc-doc/html/libraries/index.html
is one of the most-visited locations in my computer :-)
For Debian, you can check where we deviate from the Haskell Platform on
On 19 June 2011 20:51, Joachim Breitner nome...@debian.org wrote:
The binary packages. Here is an example for how we make sure that an ABI
incompatible change to web-routes requires a rebuild of yesod, and that
until that happens the user will not get the new web-routes package
installed.
$
Hi,
Am Sonntag, den 19.06.2011, 20:59 +1000 schrieb Ivan Lazar Miljenovic:
So the Debian Haskell team then has to update the apt package when
there's an ABI mismatch (that is, a dependency has been updated or
rebuilt with a new ABI)? Or is this done automagically somehow for
the user?
we
On 18 Jun 2011, at 20:19, Jack Henahan wrote:
but the dev would either be forced into Hugs, or they'd have to implement a
more portable GHC. Does such a thing exist already?
Just as a point of interest, the original nhc compiler was original written for
an ARM architecture machine (Acorn
Hi,
the haddock information generated on hackage lists class instances per
class and per data type e.g. on
http://hackage.haskell.org/packages/archive/base/4.3.1.0/doc/html/Data-Eq.html
or
http://hackage.haskell.org/packages/archive/xhtml/3000.2.0.1/doc/html/Text-XHtml-Transitional.html
For some
On 6/19/11 3:52 AM, Bas van Dijk wrote:
Hello,
I have a question about the semantics of finalizers of ForeignPtrs: If
an in scope value has a reference to a ForeignPtr is the foreign object
always kept alive, even if that reference is not used? Or do I always
need to wrap each computation, which
On 19 June 2011 14:13, wren ng thornton w...@freegeek.org wrote:
The documentation claims that
the finalizers are run only once the ForeignPtr becomes unreachable, which
implies that keeping the ForeignPtr is sufficient to keep the foreign
object alive.
Right, that was also my thinking when
On Sun, Jun 19, 2011 at 12:59 AM, Ivan Lazar Miljenovic
ivan.miljeno...@gmail.com wrote:
On 19 June 2011 13:48, Tom Murphy amin...@gmail.com wrote:
Hi List,
If my choice of Lunix distro depended 100% on its solidness as a
Haskell devel platform (I am), what would you all recommend?
In no
Right now I write a quite heavy transformation of Haskell source code
and found some strange behaviour of typechecker.
Some prerequisites:
-- dummy class. My own class is much bigger, but I
-- could reproduce that behaviour with that class.
class ToWires a
-- a type with phantom type arguments.
On 6/19/11, Arlen Cuss cel...@sairyx.org wrote:
In no particular order, the following seem to have good Linux support:
Gentoo, Arch, Fedora and Debian (I think Testing).
Please allow me to register my amusement at the idea of a distribution
with good Linux support. :D
I was very surprised
On Jun 19, 2011 9:58 AM, Antoine Latter aslat...@gmail.com wrote:
I'd be afraid of optimizations getting ride of the constructor, and since
I'm not using all of the fields I would no longer have a reference to the
foreign ptr.
Since withForeignPtr touches the foreign pointer the
Cool. It works.
Thank you very much!
2011/6/19 Miguel Mitrofanov miguelim...@yandex.ru:
Seems like let-generalization is at work here.
Types of all values in the where section are inferred basically as if they
are declared at the top level. Therefore, inheritance fails without
On 6/18/11, Alexander Solla alex.so...@gmail.com wrote:
Since the iPhone OS is pretty much OS X for ARM, and GHC apparently now
supports cross-compilation, you can compile GHC for iOS.
Can you provide a link for info? I don't understand how this would be done.
Thanks
Tom
Sending to the list as well.
On Jun 19, 2011 9:58 AM, Antoine Latter aslat...@gmail.com wrote:
On Jun 19, 2011 7:49 AM, Bas van Dijk v.dijk@gmail.com wrote:
On 19 June 2011 14:13, wren ng thornton w...@freegeek.org wrote:
The documentation claims that
the finalizers are run only once
Well, strictly speaking, GHC only supports self-cross-compilation, id est
porting[1], cf. [2]. For more information on cross compilation generally, refer
to the wiki page[3]. Does that answer your question, or did you have something
else in mind?
Seems like let-generalization is at work here.
Types of all values in the where section are inferred basically as if they
are declared at the top level. Therefore, inheritance fails without
NoMonomorphismRestriction.
There is a proposal (from Big Simon) to remove let-generalization:
On Sun, Jun 19, 2011 at 8:44 AM, Tom Murphy amin...@gmail.com wrote:
On 6/18/11, Alexander Solla alex.so...@gmail.com wrote:
Since the iPhone OS is pretty much OS X for ARM, and GHC apparently now
supports cross-compilation, you can compile GHC for iOS.
Can you provide a link for info?
20 matches
Mail list logo
