> Let It Be > ======= > > > When I find my code in tons of trouble, > > Friends and colleages come to me, > > Speaking words of wisdom: > > "Write in C." > > > > As the deadline fast approaches, > > And bugs are all that I can see, > > Somewhere, someone whispers: > > "Write in C." > > > > Write in C, write in C, > > Write in C, oh, write in C. > > LISP is dead and buried, > > Write in C. > > > > I used to write a lot of FORTRAN, > > For science it worked flawlessly. > > Try using it for graphics! > > Write in C. > > > > If you've just spent nearly 30 hours > > Debugging some assembly, > > Soon you will be glad to > > Write in C. > > > > Write in C, write in C, > > Write in C, yeah, write in C. > > Only wimps use BASIC. > > Write in C. > > Write in C, write in C > > Write in C, oh, write in C. > > Pascal won't quite cut it. > > Write in C. > > > > { > > Guitar Solo > > } > > > > Write in C, write in C, > > Write in C, yeah, write in C. > > Don't even mention COBOL. > > Write in C. > > > > And when the screen is fuzzy, > > And the editor is bugging me. > > I'm sick of ones and zeros, > > Write in C. > > > > A thousand people sware that T.P. > > Seven is the one for me. > > I hate the word PROCEDURE, > > Write in C. > > > > Write in C, write in C, > > Write in C, yeah, write in C. > > PL1 is 80s, > > Write in C. > > > > Write in C, write in C, > > Write in C, yeah, write in C. > > The government loves ADA, > > Write in C. > > Yellow Submarine > ================ > > > In the town I went to school > > There lived a man who hacked all night > > And he told us of his life > > In the land of Subroutines. > > > > So we wrote some programs > > In Pascal, C, or Scheme > > And we saved upon the disk > > Our Recursive Subroutines. > > > > We all live in a Recursive Subroutines, > > Recursive Subroutines, Recursive Subroutines. > > We all live in a Recursive Subroutines, > > Recursive Subroutines, Recursive Subroutines. > > > > All our pointers are declared > > Many arguments are also there > > And the code begins to run ... > > We all live in a Recursive Subroutines, > > Recursive Subroutines, Recursive Subroutines. > > We all live in a Recursive Subroutines, > > Recursive Subroutines, Recursive Subroutines. > > > > As we compile from memory > > Every line is error-free > > /* Comment lines are in-between */ > > In our Recursive Subroutines. > > > > We all live in a Recursive Subroutines, > > Recursive Subroutines, Recursive Subroutines. > > We all live in a Recursive Subroutines, > > Recursive Subroutines, Recursive Subroutines. > > > > We all live in a Recursive Subroutines, > > Recursive Subroutines, Recursive Subroutines. > > We all live in a Recursive Subroutines, > > Recursive Subroutines, Recursive Subroutines. > > ..................................................................... >... > > > In the town from which I came > > Lived a man who programmed games. > > And he showed us lots of scenes > > From the mass of subroutines. > > > > We rewrote one just for fun, > > but when we hit F5 it wouldn't run. > > There's a bug that can't be seen > > In the yellow subroutine. > > > > We all debug the yellow subroutine, > > yellow subroutine, yellow subroutine. > > We all debug the yellow subroutine, > > yellow subroutine, yellow subroutine. > > > > There are lots of bugs right here. > > Many more are very near. > > We must hunt, for we're not seers, > > Until all the bugs have been cleared. > > > > For every one that we have found > > Two more come, and us confound. > > We will not rest; we won't be riled > > Until the program has compiled. > > > > We all debug the yellow subroutine, > > yellow subroutine, yellow subroutine. > > We all debug the yellow subroutine, > > yellow subroutine, yellow subroutine. > > > > After compilation does succeed, > > Line by line, our code we read. > > We do peruse for logic goofs, > > Our code acts like it's aloof. > > > > We go back and code some more > > We forgot what we wrote before. > > We deleted it, and now, > > We're in trouble, and so, somehow > > Yesterday > =========== > > > Yesterday, > > All those backups seemed a waste of pay > > Now my database has gone away > > Oh, I believe in yesterday > > > > Suddenly, > > There's not half the files there used to be > > There's a deadline hanging over me > > The system crashed so suddenly > > > > I - pushed - something wrong > > What it was I could not say > > > > Now - all my data's gone > > and I long for yesterday-ay-ay-ay > > Yesterday, > > The need for back-ups seemed so far away > > I knew my data was all here to stay > > Now I believe in yesterday > > Nowhere man > =========== > > > He's a real UNIX Man > > Sitting in his UNIX LAN > > Making all his UNIX .plans > > For nobody > > > > He's as wise as he can be > > Programs in lex, yacc and C > > UNIX Man, can you help me > > At all? > > > > UNIX Man, please listen > > My printout is missin' > > UNIX Man > > The wo-o-o-orld is your 'at' command > > Blowin' in the wind > =============== > > > 1. How many code must a man type in > > Before you can call him a man? > > How many C must a compiler process > > Before it can sleep in the RAM? > > How many times must MS-DOS crash > > Before it is forever banned? > > > > R. The answer, my friend > > Is not a boolean > > The answer is not a boolean. > > > > 2. How many times must a man read his source > > Before he can see what is wrong? > > How many memory must his system have > > Before he can use 'unsigned long'? > > How many errors will it take till he knows > > That there's still some work to be done? > > > > 3. How many years can a program exist > > Before it's erased from drive C:\ ? > > How many years must known bugs exist > > Before you get an update for free? > > How many times can a drive move its head > > And pretend there's no data to read?