What if you are depending on a library written by someone not as fscking brilliant as yourself? If that library has a bug and throws an exception you will have to deal with it. You may even have to propagate the exception up to be handled by someone else. That may require some cleanup.
Besides, bugs are not the only conditions to trigger exceptions. Unusual but possible events can do it as well. Out of disk or memory conditions are such examples. Some idiot/rogue user may delete a needed file from the command line and so forth.
There's a project called InfoLeg Trying to do exactly this... I'm not sure if they've been able to keep up, but they have a lot of content browsable in a way that resembles revision control a lot.
As an example you have here our copyright law passed in 1933. The three links there can show you the original text, the most recent text applying all updates (i.e. "HEAD"
That's more or less what you were looking for? I know people who were close to the project in the past, I can get you a couple of names if you're really interested...
Microsoft has told skydivers that they don't recommend using parachutes, because a parachute adds to their weight.
This (as the advice stated by microsoft) is based on strictly true facts (greater attack area) but it is also strictly useless advice...
UNIX is hot. It's more than hot. It's steaming. It's quicksilver lightning with a laserbeam kicker. -- Michael Jay Tucker