While I do agree that any improvement to the documentation is good, I'd like to point out that every computer language has a number of foibles that are generally only learned by a programmer when he or she sits down and writes a test case. To give you a good example, eval blocks can be used to catch an exception (although it's something of a kludge to stop premature exiting of the program). It would seem logical that you could use an eval block to stop the "No Module in @INC" error and check whether or not you've got a Module, but you can't (Perl will exit anyways). Things like this are never learned by reading a FAQ or a book, but as a result of experience.