RE: Overlapping and incoherent instances

2014-08-05 Thread Simon Peyton Jones
| >>Here's one concern I have with the deprecation of | >>-XOverlappingInstances: I don't like overlapping instances, I find | >>them confusing and weird and prefer to use code that doesn't | >>include them, because they violate my expectations about how type | >>classes work. When there is a singl

Re: Old code broken by new Typeable class

2014-08-05 Thread Edward Kmett
If you can't change the definition you can use the syntax Björn Bringert added back in 2006 or so for StandaloneDeriving. Just turn on {-# LANGUAGE StandaloneDeriving, DeriveDataTypeable #-} and then you can use deriving instance Typeable Foo -Edward On Tue, Aug 5, 2014 at 1:47 PM, Volker Wy

Re: Old code broken by new Typeable class

2014-08-05 Thread Volker Wysk
Am Dienstag, 5. August 2014, 13:59:26 schrieb Brandon Allbery: > On Tue, Aug 5, 2014 at 1:47 PM, Volker Wysk > > So you need to be able to change the definition of the data type, in order > > to > > add deriving (Typeable). It's not possible to add a Typeable instance > > declaration later. > > A

Re: Old code broken by new Typeable class

2014-08-05 Thread Carter Schonwald
thats what i meant. I meant you can't WRITE the body of a typeable in 7.8, you can derive though On Tue, Aug 5, 2014 at 1:59 PM, Brandon Allbery wrote: > On Tue, Aug 5, 2014 at 1:47 PM, Volker Wysk > wrote: > >> Am Dienstag, 5. August 2014, 12:46:23 schrieb Carter Schonwald: >> > i assume 7.6

Re: Old code broken by new Typeable class

2014-08-05 Thread Brandon Allbery
On Tue, Aug 5, 2014 at 1:47 PM, Volker Wysk wrote: > Am Dienstag, 5. August 2014, 12:46:23 schrieb Carter Schonwald: > > i assume 7.6 and 7.8, if we're talking GHC rather than GCC :) > > > > in 7.8 you can't define userland typeable instances, you need only write > > deriving (Typeable) and you'r

Re: Old code broken by new Typeable class

2014-08-05 Thread Volker Wysk
Am Dienstag, 5. August 2014, 12:46:23 schrieb Carter Schonwald: > i assume 7.6 and 7.8, if we're talking GHC rather than GCC :) > > in 7.8 you can't define userland typeable instances, you need only write > deriving (Typeable) and you're all set. > add some CPP to select the instances suitable So

Re: Old code broken by new Typeable class

2014-08-05 Thread Volker Wysk
Am Dienstag, 5. August 2014, 12:49:29 schrieb Carter Schonwald: > more concretely > #if defined(__GLASGOW_HASKELL__) && ( __GLASGOW_HASKELL__ >= 707) > --- do the deriving version here I can't do a deriving version, because ProcessStatus is part of the GHC libraries (System.Posix.Process). Its d

Re: Old code broken by new Typeable class

2014-08-05 Thread adam vogt
Hi Volker, You can use this extension: http://www.haskell.org/ghc/docs/latest/html/users_guide/deriving.html#stand-alone-deriving to write that orphan Typeable instance for most ghcs (probably 6.10 is the earliest). It might be worth pushing for a Typeable instance to be added to the unix package

Re: Old code broken by new Typeable class

2014-08-05 Thread Carter Schonwald
more concretely #if defined(__GLASGOW_HASKELL__) && ( __GLASGOW_HASKELL__ >= 707) --- do the deriving version here #else --- your current stuff #endif On Tue, Aug 5, 2014 at 12:46 PM, Carter Schonwald < carter.schonw...@gmail.com> wrote: > i assume 7.6 and 7.8, if we're talking GHC rather than

Re: Old code broken by new Typeable class

2014-08-05 Thread Carter Schonwald
i assume 7.6 and 7.8, if we're talking GHC rather than GCC :) in 7.8 you can't define userland typeable instances, you need only write deriving (Typeable) and you're all set. add some CPP to select the instances suitable On Tue, Aug 5, 2014 at 12:41 PM, Volker Wysk wrote: > Hi! > > I've been

Old code broken by new Typeable class

2014-08-05 Thread Volker Wysk
Hi! I've been working with GHC-4.6.3, and updating to GHC-4.8.3 breaks my code, because the Typeable class has been changed. The compiler produces this message: - src/HsShellScript/ProcErr.chs:2294:4: ‘typeOf’ is not a (visible) method of class ‘Typeable’ - I want to def

Re: Cross compiling for Cortex A9

2014-08-05 Thread Michael Jones
I ran the same program on my dev linux and compared it to see if there were clues. On my dev box (Ubuntu) here are some snippets of the log (working app) new task (taskCount: 1) cap 0: created thread 1 new bound thread (1) cap 0: schedule() cap 0: running thread 1 (ThreadRunGHC) New weak pointe