Say I have code like below. If I comment the leftover in main, I got (Just
"L1\n", Just "L2\n", Just "L3\n", Just "L4\n"). But if I did not comment
the leftover, then I got (Just "L1\n", Just "L1\n", Just "", Just "L2\n").
Why is not it (Just "L1\n", Just "L1\n", Just "L2\n", Just "L3\n")?
takeLin
Thanks Brandon.
I've patched:
/Library/Frameworks/GHC.framework/Versions/7.4.2-x86_64/usr/lib/ghc-7.4.2/libHSrts-ghc7.4.2.dylib
and
/Library/Frameworks/GHC.framework/Versions/7.4.2-x86_64/usr/lib/ghc-7.4.2/ibHSrts_thr-ghc7.4.2.dylib
both pointing to:
/Library/Frameworks/GHC.framework/Versions
[Apologies for multiple postings.]
Vector Fabrics is hiring: we are looking for a top-notch programmer to
extend our program-analysis and parallelization products. You design
and implement algorithms to assist the programmer to create a parallel
design from a sequential C or C++ program. You work
On Mon, Apr 8, 2013 at 12:10 AM, Luke Evans wrote:
> Unfortunately, it looks like my cabal build failure occurs in a temporary
> and very short-lived directory. So presumably the dodgy FFI gets copied
> into there from elsewhere. I wonder if I can find the source...
It's running an executable
Ah, I see GHC bug #5982, which smells awfully similar.
The bug suggests a fix along the lines of:
install_name_tool /usr/local/lib/ghc-7.4.1/libHSrts-ghc7.4.1.dylib -change
/Users/ian/zz64/ghc-7.4.1/libffi/build/inst/lib/libffi.5.dylib
/usr/local/lib/ghc-7.4.1/libffi.dylib
Presumably this is sti
I'm trying to get LLVM 3.0 installed and then have the llvm-3.0.1.0 package
install and bind against it with cabal.
I'm on a recent 64 bit Mac which shows up in various messages like: "Target
platform inferred as: x86_64-apple-darwin"
I was advised on the Haskell IRC channel to install a 3.0 LL
A swapped order probably appeals to most haskellers (by contrast I
first learned ML). The real difference is that the Haskell books will
focus on lazy languages. If your tastes are in implementing fast lazy
languages using graph reduction then you may also be interested in
[1]: although I haven't
You beat me to it although I'd reverse the order of your list.
Also I wouldn't ignore the classic,
http://www.amazon.com/Compilers-Principles-Techniques-Tools-Edition/dp/0321486811
but know that it has next to nothing useful specific to FP languages,
and certainly not lazy languages.
Tommy
On Ap
On 8 April 2013 07:12, Roman Cheplyaka wrote:
> Looks like a bug in cpphs to me (CC'ing Malcolm). It should respect
> comments. E.g. GNU cpp strips C comments.
Not quite: http://hackage.haskell.org/trac/ghc/ticket/4836
>
> Roman
>
> * John MacFarlane [2013-04-05 16:04:32-0700]
>> I like markdow
On 8/04/2013, at 11:21 AM, Levent Erkok wrote:
> It appears that the consensus is that this is a historical definition dating
> back to the times when IEEE754 itself wasn't quite clear on the topic itself,
> and "so nobody thought that hard about negative zeroes." (The quote is from a
> comment
Hello all,
I definitely do not want to create a yet another thread on handling of
floating-point values in Haskell. My intention is only to see what can be
done to make it more "compilant" with IEEE754. (Also, my interest is not a
theoretical one, but rather entirely practical: I'm interested in u
Looks like a bug in cpphs to me (CC'ing Malcolm). It should respect
comments. E.g. GNU cpp strips C comments.
Roman
* John MacFarlane [2013-04-05 16:04:32-0700]
> I like markdown and use it all the time. While I acknowledge the
> problems that have been pointed out, markdown has the advantage o
I'm happy to announce new binary-conduit [1] library, that's a
serialization/deserialization
library for using binary [2] package.
[1] http://hackage.haskell.org/package/binary-conduit
[2] http://hackage.haskell.org/package/binary
--
Alexander
___
Hask
Hi,
A late reply, I was a bit busy. My comments are inline
On Thu, Apr 4, 2013 at 7:30 PM, Tillmann Rendel <
ren...@informatik.uni-marburg.de> wrote:
> Hi,
>
> L Corbijn wrote:
>
>> I'm happy to announce the release of my first package antiquoter, a
>>
>> combinator library for writing quasiquo
I disagree about the recommendation for Modern Compiler Design: I
found it to be a pretty good introduction to compiler technology, but
not functional programming with compilers, it's coverage was *very*
shallow.
By contrast, I can recommend both Compiling with Continuations (the
"standard" text o
On Sat, Apr 6, 2013 at 10:34 PM, Andrés Sicard-Ramírez <
andres.sicard.rami...@gmail.com> wrote:
> Juan, te puede interesar
>
> On Sat, Apr 6, 2013 at 5:56 PM, Sergey Bushnyak <
> sergey.bushn...@sigrlami.eu> wrote:
>
>> I will recommend you book "Modern Compiler Design" by Dick Grune and
>> other
Krzysztof Skrzętnicki gmail.com> writes:
> see this documentation on profiling with TH:
http://www.haskell.org/ghc/docs/7.6.1/html/users_guide/template-haskell.html#id624714
"GHC cannot load the profiled object code
and use it when executing the splices."
That means I do not get profiling inf
This one[1] sounds so awesome! I just read the paper.
In particular I like how one could access the current call stack
structure live.
However, the most recent changes to the code are from early 2009.
Anyone knows what happened to this?
[1]
http://hackage.haskell.org/trac/ghc/wiki/ExplicitCa
On Sun, Apr 7, 2013 at 5:03 AM, Ömer Sinan Ağacan wrote:
> That's interesting, thanks! Do you have any recommendations about
> which file to start reading? AFAIK, GHC is _huge_.
Without a discussion of your interests, it's hard to say. Certainly,
I'd set up the reading environment, namely an edit
Books about compilers is rare artifact, in comparison to some technology
books. It is uncommon to see topics on compilers for functional languages.
I was surprised, when saw it in "Modern Compiler Design", which I've
mentioned earlier. "Compiler design" series from Springer maybe reveal
topics
20 matches
Mail list logo
