On Thu, Aug 04, 2011 at 12:51:01PM +0100, Simon Marlow wrote:
> On 04/08/2011 05:35, Jens Petersen wrote:
> >On 3 August 2011 19:01, Jens Petersen wrote:
> >
> >Unexpected failures:
> >[...]
> >ffi/should_run fed001 [bad exit code] (normal)
> >[...]
> >
> >from
> >http://koji.fedorap
On Fri, Aug 5, 2011 at 12:02 AM, Simon Peyton-Jones
wrote:
> | data LiteralDesugaring m =
> | LiteralDesugaring
> | { desugarInt :: MonadThings m => Integer -> m CoreExpr
> | , desugarWord :: MonadThings m => Integer -> m CoreExpr
> ...
>
> I am not sure why you want to control the d
| > So then parseDynamicFlags should be split into two layers, the lower
| > layer returning unused flags, and the upper layer generating errors.
|
| It's not that simple. In
| ghcjs -O -someflag something -Wall
| is "something" an argument to someflag, or a file to be compiled?
It think it w
| data LiteralDesugaring m =
|LiteralDesugaring
| { desugarInt :: MonadThings m => Integer -> m CoreExpr
| , desugarWord :: MonadThings m => Integer -> m CoreExpr
...
I am not sure why you want to control the desugaring of literals. Why
literals? And why is literals enough?
| B
On 04/08/2011 05:35, Jens Petersen wrote:
On 3 August 2011 19:01, Jens Petersen wrote:
Thanks! I have done a test build in Fedora's buildsystem:
(Note this is a "bootstrap" build without shared libraries.)
Ok I did a more normal build today with shared libs and ran the testsuite too:
http:/
On Wed, Aug 3, 2011 at 2:44 PM, Simon Marlow wrote:
> On 03/08/2011 11:09, Victor Nazarov wrote:
>>
>> On Wed, Aug 3, 2011 at 11:30 AM, Simon Peyton-Jones
>> wrote:
>
>>> So perhaps that's the problem. parseDynamicFlags could perfectly well
>>> simply return any un-recognised flags. Indeed, I th
| I had a bit of fun recently tracking down quoting issues with the
| "system" command in Windows. For the examples below, I'll consistently
| use "Windows> " as the beginning of some text sent to the Windows
| command prompt cmd.exe, and use "GHC> " as the beginning of some text
| sent to a ghci s
