5 ms·
My copy of Learn You a Haskell ends on page 360 and the index is another 16 pages. Is this some weirdly shaped PDF of it with tiny phone-sized pages?
by 1-more 4y ago
My copy of Learn You a Haskell ends on page 360 and the index is another 16 pages. Is this some weirdly shaped PDF of it with tiny phone-sized pages?
- sli 4y agoAccording to its listing on the No Starch website[0], the PDF is (currently) 400 pages. I'm not a fan of that particular Haskell book but it's in no way even close to 881 pages. [0]: https://nostarch.com/lyah.htm https://nostarch.com/lyah.htm
- b112 4y agoThat's 800 pages double sided! Simply because the back side is blank, is no reason to nitpick.
- tremon 4y agoI don't get it. Wouldn't 800 pages double-sided require a PDF containing 1600 pages?
- b112 4y agoSorry, been looking at new cars, and salespeople have been explaining new car, extended warranties to me.
- stonemetal12 4y ago400 single sided printed pages. If you are trying to inflate the page count that is 800 pages, but every other page is blank.
- deleted 4y ago[deleted]
- Kalq 4y agoWhy don't you like that book and which Haskell book would you recommend then?
- vonwoodson 4y agoCould be, now that you mention it. Which, now, makes me wonder if my K&R is even shorter.
- zh3 4y agoJust checked my first edition K&R (copyright date 1978, last page number is 228 (end of index) after which there is a single tearout page for other "High Quality C and Unix system titles" from Prentice Hall. There's also a front section that has about 10 pages in roman numerals (2 pages of prefix starting with 'ix') so about 240 pages total. Page 1 starts: "Chapter 0: Introduction".
- checkyoursudo 4y agoPage 1? What, it's not zero indexed?
- DonHopkins 4y agoIt looks like it's 1-indexed, but it core dumps when you get to the last page.
- DonHopkins 4y agoThere's one thing that's usually true about every well used copy of K&R, and that's that it always opens up easily and by default to the page with the huge operator precedence order and associativity table, because that's the page everyone needs to refer to the most often, which is usually bookmarked, but in an old copy doesn't even need to be. That says something about the C programming language design, that I as a deeply stack based FORTH programmer and explicitly parenthetical LISP programmer find horrible.
- dahfizz 4y agoJust use parentheses if you're doing many operations on one line? This is common sense in any programming language. I've been programming in C for years and never had an issue with operator precedence.