The UNIX philosophy: if something doesn't work, fix it. The code is available and commented to a fault.

The DOS philosophy: if something doesn't work, get a new one or make one yourself. The program DEBUG is a wonderful place to start.

The GCC philosophy: make something do simple little tasks and put it together in a large program with a now-pointless acronym. Oh, and give no warranty, and link lots and lots of useless and complicated libraries, and spend hours finding bugs in a single configure file.

Choose one. Meanwhile, I'll be ed-ding /dev/sdC0/fossil to find all occurrences of the string "exits" and move them to where they are just to see ed blow up. (Seriously, you won't get far with ed-ding a partition - I tried).

On Dec 24, 2007, at 12:24 PM, Joel C. Salomon wrote:

On Dec 24, 2007 12:25 AM, erik quanstrom <[EMAIL PROTECTED]> wrote:
i'd be willing to give it a pass if it whined a bit, but aborting
on user input is a bit antisocial.

"Here I am, brain the size of a planet, and they ask me to move lines
around and back, doing nothing.  Call that job satisfaction, 'cause I
don't.  Excuse me while I go and abort()."

--Joel

Reply via email to