| abi compatibility would be very nice to have (if the library/binding
| code
| doesn't change, newer ghc major versions should still be able to link
| to
| bindings compiled with older ones). that is only going to become more
| important as fewer libraries are going to be shipped with ghc itself
That is all true. ABI compatibility would be nice. But I don't see how
to combine with GHC's other goals. Notably, we frequently add new
information to interface files, and it would be a major constraint not to
be able to do so.
that is the bit i never quite understood: if newer formats
I'm not sure if you're talking about C++ ABIs or C ABIs? If you're already
using a C ABI, and you're getting incompatibilities, well I have nothing
useful to say :-)
If you're talking about C++ ABIs, technically it's possible to use a
Generator to drop-down into a C ABI, pump across the
| You're right, that's annoying. It's particularly a problem for Windows
| GHC users who expect pre-built binaries, since GHC currently requires
| all libs to be rebuilt with each new minor GHC version.
Are you sure? We try hard not to change interface-file format or calling
conventions between
On 7/19/07, Claus Reinke [EMAIL PROTECTED] wrote:
the idea is well known: build your app as a server, and put
an ajax-based gui in front of it, even if server and browser
run on the same machine.
A more desktopy alternative: http://www.gtk-server.org/
martin
| You're right, that's annoying. It's particularly a problem for Windows
| GHC users who expect pre-built binaries, since GHC currently requires
| all libs to be rebuilt with each new minor GHC version.
Are you sure? We try hard not to change interface-file format or
calling conventions
On Thu, 2007-07-19 at 12:07 +0100, Claus Reinke wrote:
the idea is well known: build your app as a server, and put
an ajax-based gui in front of it, even if server and browser
run on the same machine.
A more desktopy alternative: http://www.gtk-server.org/
that looks promising. does
On Thu, 2007-07-19 at 10:06 +0100, Simon Peyton-Jones wrote:
| You're right, that's annoying. It's particularly a problem for Windows
| GHC users who expect pre-built binaries, since GHC currently requires
| all libs to be rebuilt with each new minor GHC version.
Are you sure? We try hard
On Thu, 2007-07-19 at 12:02 +0100, Claus Reinke wrote:
is there even tool support for i've got a new major version of ghc, please
rebuild and register everything i had registered for the old major version.?
Gentoo has such a tool. The ghc ebuild instructs users to run
ghc-updater after
On Thu, 2007-07-19 at 13:01 +0100, Duncan Coutts wrote:
On Thu, 2007-07-19 at 10:06 +0100, Simon Peyton-Jones wrote:
| You're right, that's annoying. It's particularly a problem for Windows
| GHC users who expect pre-built binaries, since GHC currently requires
| all libs to be rebuilt with
is there even tool support for i've got a new major version of ghc, please
rebuild and register everything i had registered for the old major
version.?
We will have soon. The nix distribution system will be able to do
exactly this.
You pass a ghc compiler for each build description. Passing
gui libs are wonderful, but haskell sometimes has too few
and sometimes has too many. and those we have do not
work with every haskell implementation. and when they do
work (usually with ghc, these days), they need to be rebuilt
whenever ghc is updated, even if the gui lib hasn't changed
at all
On Thu, 2007-07-19 at 00:12 +0100, Claus Reinke wrote:
gui libs are wonderful, but haskell sometimes has too few
and sometimes has too many. and those we have do not
work with every haskell implementation. and when they do
work (usually with ghc, these days), they need to be rebuilt
13 matches
Mail list logo
