Tuesday, June 14, 2011

documenting errors

You are looking for quick and dirty tutorial to learn some tool, with which you are hoping to finish your work before seemingly impossible deadline. You pick up a tutorial and after a line of usage description it explains 100 error codes. What would you feel. This is Bruce Barnett has to say in his Sed tutorial.

The Solaris on-line manual pages for sed are five pages long, and two of those pages describe the 34 different errors you can get. A program that spends as much space documenting the errors than it does documenting the language has a serious learning curve.

he goes again while explaining streams
Sed is the ultimate stream editor. If that sounds strange, picture a stream flowing through a pipe. Okay, you can't see a stream if it's inside a pipe. That's what I get for attempting a flowing analogy. You want literature, read James Joyce. 


No comments:

Post a Comment