7 ms·
Programs to Read
- danso 11y agoThis page has obviously been around for awhile (or at least looks like it has :))...but one thing I didn't notice until recently is that Knuth is apparently still updating it with new programs. If you scroll to the bottom, there's at least one program labeled as "August 2015"
- Jun8 11y agoFor those who may be new to Literate Programming, here's information on how to process CWEB files: http://www.readytext.co.uk/?p=2475 http://www.readytext.co.uk/?p=2475
- ilurk 11y agoTIL about cweb. [1] > CWEB is a version of WEB for documenting C, C++, and Java programs. WEB was adapted to C by Silvio Levy in 1987, and since then both Knuth and Levy have revised and enhanced the system in many ways, notably to support C++ and ANSI C. Thus CWEB combines TeX with today's most widely used professional programming languages. > If you are in the software industry and do not use CWEB but your competitors do, your competitors will soon overtake you---and you'll miss out on a lot of fun besides. I guess it never took off due to the "I'll do it latter when I have time mantra". Documenting and testing are always seen as low priority. Trying to convert maxcliques.w but it rightfully warns about missing gb_types.w Is there a zip file with all programs and dependencies? texlive-binaries ctangle also seems to be losing some formatting. [1] http://www-cs-faculty.stanford.edu/~uno/cweb.html http://www-cs-faculty.stanford.edu/~uno/cweb.html
- angersock 11y agoNobody's business was ever ruined because of bad documentation, sadly. Literate programming is an interesting idea from academia, but in the engineering environment of most startups it's a waste of time. Our program sources are annoying byproducts of a business, not something of value unto themselves.
- Retra 11y agoJust because it doesn't make you money doesn't mean it has no value.
- angersock 11y agoThere is no engineering without dollar signs in the equation. I didn't say it had no value in general, just in a particular context.
- tikhonj 11y agoNobody's business was ever obviously, directly ruined because of bad documentation, and so nobody was ever blamed for it or fired over it.
- jlg23 11y ago> Nobody's business was ever ruined because of bad documentation, sadly. I've seen quite a few startups fail because they had a smart, but completely undocumented code base. Then the smart programmers leave and who is left cannot handle the code and new hires take too long to get into it. Then funding runs out and the apparent lack of progress ensures that nobody wants to put more money into the company. > Literate programming is an interesting idea from academia, but in the engineering environment of most startups it's a waste of time. Amazingly, we're actually getting back to something that resembles literate programming - via TDD. Instead of asking for a proper spec, we now ask for test definitions that the code must pass. Those can even be written in something that is pretty close to natural language (cucumber etc) so that management can write them. Then we spend time to make the test framework understand all those pseudo-natural-language test definitions and then we finally write the code. Is that really faster? Or are we just missing the tools that would allow us to tie a natural language specification to code?
- copperx 11y ago> pretty close to natural language (cucumber etc) so that management can write them This sounds so familiar ...
- jf 11y agoI was able to get CWEB working on my mac as follows: wget http://www-cs-faculty.stanford.edu/~uno/programs/sat0.w brew install cweb cweave sat0.w tex sat0.tex dvips sat0.dvi "tex" and "dvips" were already on my system and I don't remember how I installed them.
- ilurk 11y agoJust got to work also. I also noticed that some code no longer compiles, at least the older programs. On my GNU/Linux box: > dependencies: wget ftp://ftp.cs.stanford.edu/pub/sgb/sgb.tar.gz tar -xzf sgb.tar.gz > documentation: cweave back-pdi.w pdftex back-pdi.tex okular back-pdi.pdf & > code: ctangle back-pdi.w gcc -o back-pdi back-pdi.c back-pdi 2 1 (I'll be damned if I'll ever get fluent in HN thread formatting)
- gpfreitas 11y agoMy guess is that you will find the necessary dependencies in the Stanford GraphBase: http://www-cs-faculty.stanford.edu/~uno/sgb.html http://www-cs-faculty.stanford.edu/~uno/sgb.html If I remember correctly, the GraphBase source files start with the gb_ prefix (sorry, I'm ony phone so can't check). Note: the Stanford GraphBase for me is an example of how a full blown library can be beautifully written in a literate style. Worth buying the hardcopy and reading it.
- mrcactu5 11y agothe algorithms look good but the code seems a bit arcane
- amelius 11y agoHmm, why haven't the processed files been posted as well?
- prestonbriggs 11y agoKnuth is posting source and you want the assembly?
- gohrt 11y agoNo, parent is asking for the rendered document. Analogy: The source is like HTML; parent is asking for the rendered document as you would view it in a web browser.
- zyxley 11y agoI'm not asking this to be snide, but as somebody generally unfamiliar with the literate programming concept - for practical purposes, what makes this different from having well-encapsulated functions with thorough commenting? For an example of what I mean, see underscore.js [1] and the prettyfied version of the source [2]. [1]: https://github.com/jashkenas/underscore/blob/master/underscore.js https://github.com/jashkenas/underscore/blob/master/undersco... [2]: http://underscorejs.org/docs/underscore.html http://underscorejs.org/docs/underscore.html
- prestonbriggs 11y agoUsing LP, comments can be arbitrarily formatted, with TeX equation handling, beautiful figures, tables, cross references, indices, table of contents, etc. Code can be presented in a way that best suits the reader (versus the writer or the compiler). Though Knuth's examples usually seem to dive right in, lacking the introduction to be provided by the latest stuff in TAOCP. When I use it, I write it like a paper decorated with code, where the code can be extracted and run. I usually include the necessary make file and perhaps some test data. Entries in figures/tables are sometimes generated automatically by the program being described. There are lots of old papers and critiques about LP, by Knuth and others. You should check 'em out.
- a_e_k 11y agoAs a fairly modern example, let me suggest "Physically Based Rendering" by Pharr and Humphreys [1]. It is a complete (and fairly large) book in the LP style. There are couple of sample chapters available online that you can view [2][3]. To me, one of the real advantages is that you can present the code and commentary in a logical structure that goes in an orderly progression of concepts for human understanding rather than the more strictly physical structure that a compiler expects. [1] http://www.pbrt.org/ http://www.pbrt.org/ [2] http://www.pbrt.org/chapters/pbrt_chapter7.pdf http://www.pbrt.org/chapters/pbrt_chapter7.pdf [3] http://www.pbrt.org/chapters/pbrt-2ed-chap4.pdf http://www.pbrt.org/chapters/pbrt-2ed-chap4.pdf
- kencausey 11y agoOne of the primary differences is that the document can be structured, i.e. ordered, to benefit readability and not for the needs of the software. At the point that source code is needed for tools the literate version can in one step be used to generate it. Even multiple files in a hierarchical directory structure can be generated from a single literate software document.
- douche 11y agoI'm not sure I see the point... You could make things much more readable by just using decent formatting and descriptive variable names. I know, it's decorated C code, and academic C code at that, but damn, some of that stuff is a mess to try to read. Maybe I've been in C#/Java/Python/JS land for too long, but javadoc/xmldoc/docstring documentation is a lot more readable. If you really want to, you can dump in markup, pictures, non-ASCII characters, etc into the html-based documentation. The more I look at it, this stuff must be a monstrosity to try to actually write. I can't see it being at all attractive, unless you were doing well-defined, algorithmic code. Or you could write it in normal C and package it as a library that people might actually use.
- boxy310 11y agoThe author is Donald Knuth, in case you didn't catch that. Since most of these are dated from the 90's, you should probably be comparing verbosity to COBOL or PASCAL and keeping in mind this was from before the ubiquity of Linux or Python, and long before Java, Javascript, or C#.
- douche 11y agoMost of them are dated from the 2000s. It's hard to miss that it's on Knuth's website. Just because it's published by one of the gods of computer science doesn't mean that it is code in a style that anyone should be encouraged to emulate.
- justin66 11y agoCWEB: the second most effective way to keep people from reading your code, after simply writing it in Lisp.
- gpfreitas 11y agoDid you use CWEAVE to convert the CWEB source to TeX? Then you can compile the TeX into a PDF that should be more readable than most source code out there. http://www-cs-faculty.stanford.edu/~uno/cweb.html http://www-cs-faculty.stanford.edu/~uno/cweb.html
- draven 11y agoUse scribble/lp2 [0] to do both ! [0] http://docs.racket-lang.org/scribble/lp.html http://docs.racket-lang.org/scribble/lp.html
- dschiptsov 11y agoI am afraid that this is a wrong recommendation - too narrow, too esoteric, too academic. I would suggest to read Norvig's old Common Lisp code from his Paradigms Of Artificial Intelligence Programming masterpiece (and the whole book, of course). AIMA and SICP are obviously good reads - the code is polished like fine poems. Norvig's new Python courses on Udacity are also absolutely wonderful, but the classic books are still the classic books. And then arc.arc, of course!)
- CmonDev 11y ago> I am afraid that this is a wrong recommendation - too narrow, too esoteric, too academic ... I would suggest to read ... Common Lisp code That is sure mainstream.
- etiam 11y agoWhich courses would those be? The Udacity offerings are starting to get many enough to be daunting to go through linearly, and searching for Norvig turns up only "Intro to Artificial Intelligence" and "Design of Computer Programs", both of which have been around for a few years now, if I recall correctly.
- lekanwang 11y agoA lecturer at Stanford CS (Keith Schwarz) also has a good collection of various implementations of interesting algorithms: http://www.keithschwarz.com/interesting/ http://www.keithschwarz.com/interesting/
- CuttlefishXXX 11y ago"Change files" are refered to quite a lot. What does that mean?