Talk:Haskell

EPub version?
In the past, there used to be a downloadable, .epub version. Would anybody be interested in producing such a rendering again? It's actually quite simple with e.g. pandoc, but I'm not sure what's involved in a multi-page document such as this Haskell book. I do know that I would REALLY love an updated version on my e-book reader. 41.13.8.195 (discuss) 16:03, 17 April 2015 (UTC)

As far as I know there was no epub version. There was and there is now again a pdf version that is optimized for ebook readers. I just updated this pdf with data for the current A4 pdf. The latex source code is attached to the A4 pdf. To generate the LaTeX source of the ebook reader optimized pdf version from it, you can use the following python code. Yours --Dirk Hünniger (discuss • contribs) 18:50, 26 April 2015 (UTC) import codecs g=codecs.open("./document/main/main.tex","r","utf8") t=g.read g.close

t=t.replace("\\begin{landscape}","") t=t.replace("\\end{landscape}","") t=t.replace("\\input{../headers/paper}","") t=t.replace("\\KOMAoptions{fontsize=9pt,DIV=90,BCOR=0pt}","") t=t.replace("\\begin{document}","""\lowertitleback{ {\\footnotesize On the 28th of April 2012 the contents of the English as well as German Wikibooks and Wikipedia projects were licensed under Creative Commons Attribution-ShareAlike 3.0 Unported license. An URI to this license is given in the list of figures on page \\pageref{ListOfFigures}. If this document is a derived work from the contents of one of these projects and the content was still licensed by the project under this license at the time of derivation this document has to be licensed under the same, a similar or a compatible license, as stated in section 4b of the license. The list of contributors is included in chapter Contributors on page \\pageref{Contributors}. The licenses GPL, LGPL and GFDL are included in chapter Licenses on page \\pageref{Licenses}, since this book and/or parts of it may or may not be licensed under one or more of these licenses, and thus require inclusion of these licenses. The licenses of the figures are given in the list of figures on page \\pageref{ListOfFigures}.}}\\begin{document}\\setlength{\\paperwidth}{3.6in} \\setlength{\\paperheight}{4.8in} \\setlength{\\pdfpagewidth}{\\paperwidth} \\setlength{\\pdfpageheight}{\\paperheight} \\KOMAoptions{fontsize=11pt,DIV=50,BCOR=0mm}\\begin{landscape}""") t=t.replace("height=6.5in","height=2.0in") t=t.replace("\\pagestyle{scrheadings}","") t=t.replace("\\tableofcontents","{ \\small \\tableofcontents }") t=t.replace("\\end{document}","\end{landscape}\\end{document}") t=t.replace("\\end{document}","\end{landscape}\\end{document}") t=t.replace("\\LaTeXDoubleBoxTemplate","\\LaTeXDoubleBoxOpenTemplate")

g=codecs.open("./document/main/main.tex","w","utf8") g.write(t) g.close

Yet Another Haskell Tutorial
Why is Yet Another Haskell Tutorial a "subbook" of this book? Shouldn't it be a separate book as Write Yourself a Scheme in 48 Hours? I.e., Haskell/YAHT should be moved to Yet Another Haskell Tutorial, Haskell/YAHT/Preamble should be moved to Yet Another Haskell Tutorial/Preamble etc. (It should also have it's own category.) --Cic (discuss • contribs) 22:32, 8 January 2015 (UTC)
 * Regardless of how the YAHT is used in that case, it actually should be *removed* from the Wikibooks entirely because its content has been absorbed and mixed into the Haskell Wikibook itself and also greatly improved in the process. Nobody should read YAHT independently now. Backfromquadrangle (discuss • contribs) 00:15, 22 September 2015 (UTC)
 * Cic has already moved the pages to a separate namespace. Given that deleting the leftover redirects would cause avoidable link rot, I guess all that is left for us to do is removing the link to YAHT from the front page (by the way, the header where it is currently under should not be named "Tutorials that have been incorporated into the Haskell Wikibook". It should be renamed "Other books about Haskell in Wikibooks" or merged with "Additional resources").--Duplode (discuss • contribs) 05:14, 22 September 2015 (UTC)

GHCi interactions are badly formatted in the pdf
In the pdf version, the lines entered at the GHCi prompt and their results are shown on a single line. There should be a line break between them as there is in the online version. Is this a bug in the pdf generator? Is it the fault of the page markup -- is there some formatting that could be added to the markup -- at least as a workaround -- that would fix the pdf version without breaking the online presentation? Pmartel60 (discuss • contribs) 02:39, 9 February 2015 (UTC)

Use of term 'Variable'
I do feel quite uncomfortable, when 'Variable' is used in texts like this on Functional Programming (Language(s)). Most starters in this area do have some experience in other/'procedural' programming languages, where variable means something like 'an area of memory who's content may vary depending on program flow', which is strongly misleading when you try to map onto functional PLs. Maybe some early paragraph about meaning of 'Variable' would help. I hope, I did make my POV clear enough, as English's not my native language.
 * I think there is explanation about this. It's still a variable in that  is a function that has a *variable* x which can be substituted with any number. It varies. It just doesn't vary within the exact same scope. Once defined for a scope, it's defined. But it can be used elsewhere and defined differently there. Please feel free to read the introductory stuff and consider adding footnotes or clearer stuff, but we need to avoid getting in depth about explaining how it works in other languages, as that is not the focus here.Backfromquadrangle (discuss • contribs) 00:19, 22 September 2015 (UTC)
 * We have a brief digression about that difference in an early chapter. As Backfromquadrangle points out, it would be unwise to emphasise comparisons to other languages, as that would make the text less accessible to readers with no procedural programming experience.--Duplode (discuss • contribs) 05:21, 22 September 2015 (UTC)

PDF/printable version headers
There's a problem that topic header like "Haskell Basics" and all its pages (Getting set up, ...) appear on the same level of header (H1 in printable HTML). In PDF version this results in an empty "chapter" for "Haskel Basics" instead of some big section title that would be more expected. In PDF they are also both on the same numbering level, which clearly is not right. Haskel Basics either should be not numbered and promoted into some higher plane or all its content should have two level numbering already. I don't know reasons behind it (problems combining a lot of pages?) but when you look at the book from this perspective (all-in-one printable HTML, PDF, ...) it definitely doesn't feel right.

incorporating good compatible material
For example, this set of lectures from a class: https://cseweb.ucsd.edu/classes/wi13/cse230-a/lectures.html are superb and really clearly presented. The content is all permissively licensed: https://github.com/UCSD-PL/230-web and I think adapting / mixing that material into the Wikibook would be great. There's probably other stuff too. I wasn't sure if there was a list around here of resources waiting to be incorporated. --Backfromquadrangle (discuss • contribs) 06:57, 29 January 2016 (UTC)

PDF version is over two years old
There are topics missing in the PDF version. How can we get an updated PDF version?

Hi, I made a first draft of a new PDF Version its here:

thumb|pdf version of english wikibook on haskell

Since I am quite busy at the moment I cannot say if or when I will be able to resolve the numerous remaining bugs in the above linked document. --Dirk Hünniger (discuss • contribs) 17:31, 26 November 2016 (UTC)

Hi, I updated the PDF version on the main page of this book. If you find any bugs, please write them down here.--Dirk Hünniger (discuss • contribs) 10:47, 27 November 2016 (UTC)

Hi, I also updated the ebook reader version. Dirk Hünniger (discuss • contribs) 11:01, 27 November 2016 (UTC)


 * Hi, Page 266 in the pdf has incorrect formatting for the phrase "In addition to the monad transformers themselves". Kindly look into fixing it. — Preceding unsigned comment added by Iambrj (talk • contribs) 02:24, 5 May 2020 (UTC)

Target audience
"Our aim in this book is to introduce you to the Haskell programming language — from the very basics to advanced features — and to computer programming in general."

Who is the target audience for this book? Is it beginner programmers or people who never did programming? —Srid  🍁 23:35, 15 November 2019 (UTC)


 * If it is the former, I'd think that the beginning paragraphs of Haskell/Getting_set_up is unnecessarily verbose. What do you think? —Srid  🍁 23:39, 15 November 2019 (UTC)


 * A general observation. When a wikibook has multiple "tracks" (or some other similar terminology), it often means the book is meant to cater to multiple audiences.  Compare Conlang. --Pi zero (discuss • contribs) 04:34, 16 November 2019 (UTC)