On 23 January 2011 00:31, austin seipp a...@hacks.yi.org wrote:
or what the current state of dynamic linking on
windows is.
AFAIK it is meant to work. What I'm not sure about is whether any of
the plugins code will have to be modified to make use of it. I suspect
it won't since IIRC I went
On 21 January 2011 23:59, austin seipp a...@hacks.yi.org wrote:
Perhaps Max can
elaborate on why this design was rejected in favor of the current one,
so we can see how and where it falls down, and what we really want.
The only reason really is that it added a lot of mechanism. From the
top of
Hi Austin,
The compiler plugins work is a great, and I'd be a likely user. The
original version wasn't supported on Windows, because GHC on Windows
lacked various forms of dynamic linking. Does the current patch you've
prepared work on Windows?
Thanks, Neil
On Sat, Jan 22, 2011 at 10:29 AM, Max
(moved into g-h-u mainline to avoid cluttering discussion around new
GHC plans. Anybody who has comments on the plugins work is encouraged
to reply here, not there.)
Neil,
Preemptive TL;DR: I don't quite know, but I'd be willing to work on it.
I seem to remember at the time Max originally did
Austin
| So, given that 7.2 will be released much earlier than the normal
| release cycle, is there any room for anything else to get into HEAD
| for the 7.2 release before everything is switched? In particular I
| fixed up Max Bolingbroke's old compiler plugin work to be usable with
| the latest
On 21 January 2011 09:13, Simon Peyton-Jones simo...@microsoft.com wrote:
I'm pretty keen on the whole plugin idea, because it makes the compiler more
extensible and lowers the barrier to entry. My only reason for delay is that
I wanted to review the design (as seen by a plug-in author).
Simon,
On Fri, Jan 21, 2011 at 3:13 AM, Simon Peyton-Jones
simo...@microsoft.com wrote:
Austin
| So, given that 7.2 will be released much earlier than the normal
| release cycle, is there any room for anything else to get into HEAD
| for the 7.2 release before everything is switched? In
Jan 2011 17:59:32
To: Simon Peyton-Jonessimo...@microsoft.com
Cc: Simon Marlowmarlo...@gmail.com;
glasgow-haskell-users@haskell.orgglasgow-haskell-users@haskell.org
Subject: Re: Release/git plans
Simon,
On Fri, Jan 21, 2011 at 3:13 AM, Simon Peyton-Jones
simo...@microsoft.com wrote:
Austin
As promised, here are our plans for forthcoming GHC releases and the git
switchover:
- do a 7.0.2 RC as soon as possible, followed shortly by a release.
Currently blocking this is a problem with Cabal that shows up on
OS X 10.6, we hope to have this resolved soon.
- switch the GHC repo
Hello Simon,
On Thu, Jan 20, 2011 at 9:48 AM, Simon Marlow marlo...@gmail.com wrote:
...
- make a new stable branch for 7.2, and release 7.2.1 shortly after.
So we'll be doing a 7.2.1 release much earlier than planned. Our motivation
for doing this is:
- the 7.0 branch is darcs, but the
On 20 January 2011 16:57, austin seipp a...@hacks.yi.org wrote:
It would be nice to have this in GHC 7.2, but I was thinking of
eventually extending the scope of compiler plugins to allow users to
write Cmm optimisations as well.
This would be particularly cool because Cmm optimisations in the
On 01/20/11 11:57, austin seipp wrote:
The GHC git repo that
we'll be using is here:
http://darcs.haskell.org/ghc.git
This is an incredibly minor note in my opinion (that was brought up
before IIRC) but, isn't it a little strange for ghc's git repository
to exist on darcs.haskell.org? Not
Point taken, I personally think it's rather minor although it was
brought up before like I said, so perhaps others think differently.
Either way, I, for one, welcome our new version control overlord.
On Thu, Jan 20, 2011 at 3:09 PM, Isaac Dupree
m...@isaac.cedarswampstudios.org wrote:
On
This is Haskell. One should abstract away the system used. Call it
vcs-ghc@ and vcs.haskell.org ;-)
Gruss,
Christian
* austin seipp a...@hacks.yi.org [20.01.2011 22:19]:
Point taken, I personally think it's rather minor although it was
brought up before like I said, so perhaps others think
14 matches
Mail list logo
