Hacker News Reader

I'm a little confused about the point the author repeatedly makes in this article, complaining about the #includes on top of the file. Genuinely curious, where does he propose to put the includes?

View on HN

With Literate Programming it would be possible to defer the mention of the includes and a discussion of why they are necessary/how they were selected to a point in the document where that makes sense and was interesting.

The problem is, that sort of mechanistic thing is difficult to make interesting, and is easier to just do an exposition dump at the beginning of the document and be done with it.

Part of my point was even if there was not an obvious place to put it, the mechanical place to put it is at the end! That's what I consistently did in the project I cited.

So I wasn't arguing for people to agonize endlessly about where to put it.

Sounds like a plan --- I'd be curious to see an example LP which does this for which it works well.

Reply on news.ycombinator.com