My problem with literate programming is finding the code.
("Literate code" usually gets buried in text, and finding it
can be frustrating.)And, sometimes, my problem with literate programming is finding the purpose of the code. (Literate programming does not guarantee good technical writing.) Basically... having a lot of comments is not at all the same as having good comments. What I want to know, when I am dealing with code, is: What does the code get used for? What data is in the domain of the code? How do the results look? Other than that, and having good names for things, comments usually just get in my way. (Of course, knowing when things changed and who made the change can be useful when dealing with problems, but that really belongs in source control and not in the code itself.) -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
