There is none
On Sun, Oct 7, 2012 at 4:27 AM, Thomas Schilling
wrote:
> Does `ghc-pkg check` report any issues?
>
> On 6 October 2012 15:24, Magicloud Magiclouds
> wrote:
>> Hi,
>> I am installing postgres hackage (cannot remember the exact name
>> right now). When it compiling the templat
>>> Do you have any suggestions to install xmobar in this particular case?
>>
>> In case of executables I usually rm -rf ~/.ghc, cabal install,
>> and rm -rf ~/.ghc again. Executables are still here (in ~/.cabal/bin),
>> but all libraries are lost. Warning: it may break your development
>> environm
Thanks!
On 06-10-2012 23:07, Yuras Shumovich wrote:
On Sat, 2012-10-06 at 22:40 +0200, José Lopes wrote:
OK. Got it!
Do you have any suggestions to install xmobar in this particular case?
In case of executables I usually rm -rf ~/.ghc, cabal install,
and rm -rf ~/.ghc again. Executables are s
On Sat, 2012-10-06 at 22:40 +0200, José Lopes wrote:
> OK. Got it!
>
> Do you have any suggestions to install xmobar in this particular case?
In case of executables I usually rm -rf ~/.ghc, cabal install,
and rm -rf ~/.ghc again. Executables are still here (in ~/.cabal/bin),
but all libraries are
I found I had to keep switching between RWH and other books for these
concepts to sink in. A really good resource that I don't see mentioned too
often is the Haskell wikibook:
http://en.wikibooks.org/wiki/Haskell
I don't remember it covering parsec specifically but if you get grounded in
all the
OK. Got it!
Do you have any suggestions to install xmobar in this particular case?
Thanks,
José
On 06-10-2012 19:08, Yuras Shumovich wrote:
On Sat, 2012-10-06 at 18:25 +0200, José Lopes wrote:
OK.
But, wouldn't it be possible for xmobar to use mtl-2.0.1.0 and for
parsec to use mtl-2.1.1, whi
Does `ghc-pkg check` report any issues?
On 6 October 2012 15:24, Magicloud Magiclouds
wrote:
> Hi,
> I am installing postgres hackage (cannot remember the exact name
> right now). When it compiling the template haskell part I got the
> following error message.
> I tried to clear all user spac
Just to explain what's going on. It looks like you are compiling a
module that uses template haskell, which in turn relies on GHCi bits.
In particular, GHCi has a custom linker for loading compiled code.
This linker is very fragile and tends to break whenever the platform
GCC/linker changes. Simil
Dnia sobota, 6 października 2012, Mark Thom napisał:
>Also, the functional pearl on applicative functors by Conor McBride and a
>second
> author (can't recall his name) blew the door open on the subject, for me.
Good to hear, it's in front of me on the desk and I'm planning to finish that
pearl t
I also had problems when I began reading RHW, early in my career as a
Haskell beginner. The functional pearl on monadic parsers by Hutton and
Meijer was a great help in understanding the thinking behind Parsec. While
reading it, I had some difficulty understanding why certain functions
should ever
I'm not totally sure if you're having problems with RWH, or think it's
too easy, but here are my thoughts on both:
Both RWH and LYAH (http://learnyouahaskell.com/) are intended for
beginners/people who just want to get started, and RWH tends to be
regarded as the hardest to understand ("read LYAH
I began learning Haskell 9 months ago. I still consider myself a beginner, but
I'm progressing
towards more advanced concepts. I read scientific papers (simpler ones) and
books about Haskell
and functional programming. Right now I'm reading Pearls of Functional
Algorithm Design,
Introduction
On Sat, 2012-10-06 at 18:25 +0200, José Lopes wrote:
> OK.
>
> But, wouldn't it be possible for xmobar to use mtl-2.0.1.0 and for
> parsec to use mtl-2.1.1, while xmobar would use this parsec version?
> In this case, I am assuming that mtl-2.0.1.0 and mtl-2.1.1 are
> considered two different lib
On 6 October 2012 17:25, José Lopes wrote:
> OK.
>
> But, wouldn't it be possible for xmobar to use mtl-2.0.1.0 and for parsec to
> use mtl-2.1.1, while xmobar would use this parsec version?
> In this case, I am assuming that mtl-2.0.1.0 and mtl-2.1.1 are considered
> two different libraries.
Pos
Hi cafe,
Where do Haskell and DPH stand in comparison to C/OpenMP w.r.t. graph
algorithms?
Are benchmarks for graph algorithms available for Haskell like the ones we
find at http://www.graphanalysis.org/benchmark/?
- Damodar
___
Haskell-Cafe mailing list
OK.
But, wouldn't it be possible for xmobar to use mtl-2.0.1.0 and for
parsec to use mtl-2.1.1, while xmobar would use this parsec version?
In this case, I am assuming that mtl-2.0.1.0 and mtl-2.1.1 are
considered two different libraries.
Thanks,
José
On 06-10-2012 17:17, Yuras Shumovich wro
On 12-10-06 05:18 AM, Johannes Waldmann wrote:
wren ng thornton freegeek.org> writes:
As for whether the default should be "infix 9" instead of "infixl 9" ...
that was exactly the point of my message. - J.
Perhaps, half of the people want infixl, another half of the people want
infixr, an
On Sat, 2012-10-06 at 17:02 +0200, José Lopes wrote:
> Hello,
Hello
>
> I'm trying to understand Cabal dependencies.
> Why does the following situation happen?
xmobar-0.15 depends on mtl-2.0.* and needs parsec
All packages that will be broken, depends on parsec.
But parsec is compiled with mtl-2
Hello,
I'm trying to understand Cabal dependencies.
Why does the following situation happen?
# cabal install xmobar --dry-run
Resolving dependencies...
In order, the following would be installed:
parsec-3.1.3 (reinstall) changes: mtl-2.1.1 -> 2.0.1.0
xmobar-0.15 (new package)
Warning: The follow
wren ng thornton freegeek.org> writes:
> As for whether the default should be "infix 9" instead of "infixl 9" ...
that was exactly the point of my message. - J.
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/l
On Fri, 05 Oct 2012 17:31:49 +0200, JP Moresmau
wrote:
Hello, I've installed Cabal and cabal-install 1.16 (which required
network) on a new GHC 7.6.1 install and everything went well, except
now when building a package requiring network I get:
Loading package network-2.4.0.1 ... ghc.exe: Unk
21 matches
Mail list logo
