Hi Alfredo,
No dark magic as far as I recall (except in the actual bundling as a Mac
app, unfortunately that required some magic, the GTK libraries don't
relocate so easily :-( ). I didn't have any problems building. I compiled
it with ghc 7.6.1, with the GTK libraries installed manually (there ar
Hi Edsko, thanks for the reply.
The only things that might affect the outcome are:
a) Ghc version: I'm running ghc 7.6.2 instead of 7.6.1
b) Don't know if you are using cabal-dev as sandboxing (like any good
Haskell programmer I'm too lazy to open your blog post :D ), whilst I'm
using hsenv
c) I'v
a) 7.6.2 vs 7.6.1 seems unlike to be the issue, although theoretically
possible I guess.
b) Actually, the blog post is how to set things up by hand for better
control than either of those tools give you; but again, I don't think it's
relevant.
c) This might be a bigger difference. I don't know what
Perfect, I will try to probe the ground for points c) and d), and I will
get back to all of you if I manage to shed some light to this mystery :D
A.
On 4 April 2013 09:12, Edsko de Vries wrote:
> a) 7.6.2 vs 7.6.1 seems unlike to be the issue, although theoretically
> possible I guess.
> b) Ac
Albert Y. C. Lai vex.net> writes:
> Quantifiers are complicated, but I don't see how explicit is more so
> than implicit. [...] I have just seen recently [...]
Great example. I completely agree.
My feeling is that mathematicians use this principle of leaving out
some of the quantifiers and p
Hi,
I proposed a bioinformatics GSoC project involving Haskell using OSC as
the mentoring organization. Typically, haskell.org projects concern
infrastructure rather than applications, and I don't know if I'm allowed
to submit both places :-)
Anyway, as this is a likely place to find prospectiv
On Thu, Apr 04, 2013 at 11:02:34AM +, Johannes Waldmann wrote:
> My feeling is that mathematicians use this principle of leaving out
> some of the quantifiers and putting some others in the wrong place
> as a cultural entry barrier to protect their field from newbies.
Albert showed an example
Hi,
Richard A. O'Keefe wrote:
As I understand it, in ML, it seemed to be a clever idea to not have type
signatures at all.
Wrong. In ML, it seemed to be a clever idea not to *NEED* type signatures,
and for local definitions they are very commonly omitted.
In the ML I used, I remember that
Tom Ellis jaguarpaw.co.uk> writes:
> I didn't see an example of quantifiers in the wrong place.
The example was:
> every x satisfies P(x,y) for some y
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/
Mateusz Kowalczyk writes:
> About two weeks ago we got an email (at ghc-users) mentioning that
> comparing to 7.6, 7.7.x snapshot would contain (amongst other things),
> type level natural numbers.
>
> I believe the package used is at [1].
>
> Can someone explain what use is such package in Haske
On Thu, Apr 04, 2013 at 01:15:27PM +, Johannes Waldmann wrote:
> Tom Ellis jaguarpaw.co.uk> writes:
> > I didn't see an example of quantifiers in the wrong place.
>
> The example was:
>
> > every x satisfies P(x,y) for some y
Oh I see. I interpreted that as lack of disambiguating parenth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/04/13 12:35, Ketil Malde wrote:
>
> Hi,
>
> I proposed a bioinformatics GSoC project involving Haskell using
> OSC as the mentoring organization. Typically, haskell.org projects
> concern infrastructure rather than applications, and I don't kn
Mateusz Kowalczyk wrote:
>What would you say is the level of bioinformatics understanding that
>one would have to have to even consider applying?
Not very much, some knowledge of string edit distance and dynamic programming
would be good, but if not, it's something I can straighten out with a
Hi all,
Haddock's current markup language leaves something to be desired once
you want to write more serious documentation (e.g. several paragraphs
of introductory text at the top of the module doc). Several features
are lacking (bold text, links that render as text instead of URLs,
inline HTML).
Hi,
L Corbijn wrote:
I'm happy to announce the release of my first package antiquoter, a
combinator library for writing quasiquoters and antiquoters. The main
aim is to simplify their definitions and reduce copy-and-paste programming.
Very interesting. I'm using something similar to your EP cl
Yes please!
-E
On Thu, Apr 4, 2013 at 5:49 PM, Johan Tibell wrote:
> Hi all,
>
> Haddock's current markup language leaves something to be desired once
> you want to write more serious documentation (e.g. several paragraphs
> of introductory text at the top of the module doc). Several features
On Thu, Apr 04, 2013 at 06:41:19PM +0100, Edsko de Vries wrote:
> Yes please!
+1 as well. I find the current syntax too restrictive…
iustin
> On Thu, Apr 4, 2013 at 5:49 PM, Johan Tibell wrote:
>
> > Hi all,
> >
> > Haddock's current markup language leaves something to be desired once
> > you
On Thu, Apr 4, 2013 at 7:49 PM, Johan Tibell wrote:
> Hi all,
>
> Haddock's current markup language leaves something to be desired once
> you want to write more serious documentation (e.g. several paragraphs
> of introductory text at the top of the module doc). Several features
> are lacking (bol
A sane markup for haddock would be greatly appreciated. I've grown
tired of noticing highlighted words arising from unescaped quotes all
over hackage.
On Thu, 4 Apr 2013 09:49:04 -0700 Johan Tibell
wrote:
> Hi all,
>
> Haddock's current markup language leaves something to be desired once
> you
On Mon, Apr 1, 2013 at 5:56 PM, Edward Z. Yang wrote:
> http://ezyang.com/papers/ezyang13-rlimits.pdf
>
Correct me if I'm wrong, but reading that I don't seem to see any tests
against actual adversarial code - just checking that the limits kick in on
a bunch of ordinary code.
--
gwern
ht
(Redirecting follow-up to haskell-cafe)
Very cool! I have been hoping someone will find a way to integrate
kuler.adobe.com with diagrams, and this will help a lot. =)
https://github.com/diagrams/diagrams-lib/issues/77
-Brent
On Wed, Apr 03, 2013 at 06:49:34PM -0500, Jeremy Shaw wrote:
> I am
On Thu, Apr 4, 2013 at 1:46 PM, Brent Yorgey wrote:
> (Redirecting follow-up to haskell-cafe)
>
> Very cool! I have been hoping someone will find a way to integrate
> kuler.adobe.com with diagrams, and this will help a lot. =)
>
> https://github.com/diagrams/diagrams-lib/issues/77
Nice! One th
On Thu, Apr 4, 2013 at 10:03 PM, Ketil Malde wrote:
> Not very much, some knowledge of string edit distance and dynamic programming
> would be good, but if not, it's something I can straighten out with a student
> in an afternoon, I think.
Just a suggestion:
People love quizzes and brain tease
I humbly suggest reStructuredText rather than Markdown, which is what
is used by the Python community for documentation. Since it's specifically
made for documentation it may be nicer. But, I don't want to spark
a format argument.
There is also the Pandoc program, which is a universal-ish markup
On Fri, Apr 5, 2013 at 3:04 AM, Simon Heath wrote:
> I humbly suggest reStructuredText rather than Markdown, which is what
> is used by the Python community for documentation. Since it's specifically
> made for documentation it may be nicer. But, I don't want to spark
> a format argument.
Could
On Thu, Apr 4, 2013 at 11:22 PM, Kim-Ee Yeoh wrote:
> On Fri, Apr 5, 2013 at 3:04 AM, Simon Heath wrote:
> > I humbly suggest reStructuredText rather than Markdown, which is what
> > is used by the Python community for documentation. Since it's
> specifically
> > made for documentation it may b
On 4 April 2013 20:49, Johan Tibell wrote:
> Hi all,
>
> Haddock's current markup language leaves something to be desired once
> you want to write more serious documentation (e.g. several paragraphs
> of introductory text at the top of the module doc). Several features
> are lacking (bold text, li
On 13-04-04 01:07 AM, wren ng thornton wrote:
When the quantifiers are implicit, we can rely on the unique human ability
to DWIM. This is a tremendous advantage when first teaching people about
mathematical concerns from a logical perspective. However, once people
move beyond the basics of quanti
On 5/04/2013, at 1:22 AM, Tillmann Rendel wrote:
> Hi,
>
> Richard A. O'Keefe wrote:
>>> As I understand it, in ML, it seemed to be a clever idea to not have type
>>> signatures at all.
>>
>> Wrong. In ML, it seemed to be a clever idea not to *NEED* type signatures,
>> and for local definitio
On Thu, Apr 4, 2013 at 9:49 AM, Johan Tibell wrote:
> I suggest that we implement an alternative haddock syntax that's a
> superset of Markdown. It's a superset in the sense that we still want
> to support linkifying Haskell identifiers, etc. Modules that want to
> use the new syntax (which will p
[I'm posting on behalf of my colleague Jesse Bingham. While Jesse and I
work for different groups at Intel, we collaborate quite often, and I do
expect to work with the intern to an extent as well. To that end, I'm happy
to answer any questions you might have. Otherwise, direct all
correspondence t
Johan Tibell writes:
> On Thu, Apr 4, 2013 at 9:49 AM, Johan Tibell wrote:
>> I suggest that we implement an alternative haddock syntax that's a
>> superset of Markdown. It's a superset in the sense that we still want
>> to support linkifying Haskell identifiers, etc. Modules that want to
>> use
There was a short thread on this in the beginners section a while back. I
think it is an exciting subject and would like to hear what others thoughts
are on it. The Windows 8 metro style apps are built using a new API that is
designed to be exposed to other languages using "language projections" wh
On 5/04/2013, at 12:34 PM, Johan Tibell wrote:
>
> Markdown has won. Look at all the big programming sites out there,
> from GitHub to StackOverflow, they all use a superset of Markdown.
Yes, but they tend to use _different_ supersets of Markdown.
Would it be too much to ask that a notation be
> Would it be too much to ask that a notation be used which has
> a formal syntax and a formal semantics?
We will document our superset, sure. That's what others did as well.
The point is using Markdown as the shared base.
___
Haskell-Cafe mailing list
On Thu, Apr 4, 2013 at 3:29 PM, Albert Y. C. Lai wrote:
> On 13-04-04 01:07 AM, wren ng thornton wrote:
>
>> When the quantifiers are implicit, we can rely on the unique human ability
>> to DWIM. This is a tremendous advantage when first teaching people about
>> mathematical concerns from a logic
+++ Simon Heath [Apr 04 13 13:04 ]:
> I humbly suggest reStructuredText rather than Markdown, which is what
> is used by the Python community for documentation. Since it's specifically
> made for documentation it may be nicer. But, I don't want to spark
> a format argument.
>
> There is also the
On 5/04/2013, at 2:00 PM, Johan Tibell wrote:
>> Would it be too much to ask that a notation be used which has
>> a formal syntax and a formal semantics?
>
> We will document our superset, sure. That's what others did as well.
> The point is using Markdown as the shared base.
Nononono.
Sure, th
On 5 April 2013 13:24, Richard A. O'Keefe wrote:
>
> On 5/04/2013, at 2:00 PM, Johan Tibell wrote:
>
>>> Would it be too much to ask that a notation be used which has
>>> a formal syntax and a formal semantics?
>>
>> We will document our superset, sure. That's what others did as well.
>> The point
On Fri, Apr 5, 2013 at 10:44 AM, Ivan Lazar Miljenovic
wrote:
> I don't think so; this was one of the big issues recently when people
> were trying to get Gruber to actually _do_ something with Markdown as
> there were all these corner cases.
In that case, surely this is an opportunity to convene
On 5 April 2013 15:49, Kim-Ee Yeoh wrote:
> On Fri, Apr 5, 2013 at 10:44 AM, Ivan Lazar Miljenovic
> wrote:
>> I don't think so; this was one of the big issues recently when people
>> were trying to get Gruber to actually _do_ something with Markdown as
>> there were all these corner cases.
>
> I
(Folks, let's rescue this increasingly tendentious thread.)
Some points to ponder:
(1) "Any" can be often be clarified to mean "all", depending on how
polymorphic functions are exegeted. In a homotopy-flavored explanation
of natural transformation, its components (read "parametric
instances") exi
I think this thread has went to became a quest for One True Markup
Language...
I would like to propose a different approach: while we are at extending
Haddock why not make it possible to choose from a set of different
documentation plugins? Something that works akin to the type: Text ->
Environmen
43 matches
Mail list logo
