Proverbs, aphorisms, quotations (English) | by Linux fortune |
Once upon a time there was a DOS user who saw Unix, and saw that it was good. After typing cp on his DOS machine at home, he downloaded GNU's unix tools ported to DOS and installed them. He rm'd, cp'd, and mv'd happily for many days, and upon finding elvis, he vi'd and was happy. After a long day at work (on a Unix box) he came home, started editing a file, and couldn't figure out why he couldn't suspend vi (w/ ctrl-z) to do a compile. (By ewt@tipper.oit.unc.edu (Erik Troan) | |
Who wants to remember that escape-x-alt-control-left shift-b puts you into super-edit-debug-compile mode? (Discussion in comp.os.linux.misc on the intuitiveness of commands, especially Emacs.) | |
As part of an ongoing effort to keep you, the Fortune reader, abreast of the valuable information the daily crosses the USENET, Fortune presents: News articles that answer *your* questions, #1: Newsgroups: comp.sources.d Subject: how do I run C code received from sources Keywords: C sources Distribution: na I do not know how to run the C programs that are posted in the sources newsgroup. I save the files, edit them to remove the headers, and change the mode so that they are executable, but I cannot get them to run. (I have never written a C program before.) Must they be compiled? With what compiler? How do I do this? If I compile them, is an object code file generated or must I generate it explicitly with the > character? Is there something else that must be done? | |
Never put off till run-time what you can do at compile-time. -- D. Gries | |
"Nuclear war can ruin your whole compile." -- Karl Lehenbauer | |
Price Wang's programmer was coding software. His fingers danced upon the keyboard. The program compiled without an error message, and the program ran like a gentle wind. Excellent!" the Price exclaimed, "Your technique is faultless!" "Technique?" said the programmer, turning from his terminal, "What I follow is the Tao -- beyond all technique. When I first began to program I would see before me the whole program in one mass. After three years I no longer saw this mass. Instead, I used subroutines. But now I see nothing. My whole being exists in a formless void. My senses are idle. My spirit, free to work without a plan, follows its own instinct. In short, my program writes itself. True, sometimes there are difficult problems. I see them coming, I slow down, I watch silently. Then I change a single line of code and the difficulties vanish like puffs of idle smoke. I then compile the program. I sit still and let the joy of the work fill my being. I close my eyes for a moment and then log off." Price Wang said, "Would that all of my programmers were as wise!" -- Geoffrey James, "The Tao of Programming" | |
THE LESSER-KNOWN PROGRAMMING LANGUAGES #13: SLOBOL SLOBOL is best known for the speed, or lack of it, of its compiler. Although many compilers allow you to take a coffee break while they compile, SLOBOL compilers allow you to travel to Bolivia to pick the coffee. Forty-three programmers are known to have died of boredom sitting at their terminals while waiting for a SLOBOL program to compile. Weary SLOBOL programmers often turn to a related (but infinitely faster) language, COCAINE. | |
THE LESSER-KNOWN PROGRAMMING LANGUAGES #14 -- VALGOL VALGOL is enjoying a dramatic surge of popularity across the industry. VALGOL commands include REALLY, LIKE, WELL, and Y*KNOW. Variables are assigned with the =LIKE and =TOTALLY operators. Other operators include the "California booleans", AX and NOWAY. Loops are accomplished with the FOR SURE construct. A simple example: LIKE, Y*KNOW(I MEAN)START IF PIZZA =LIKE BITCHEN AND GUY =LIKE TUBULAR AND VALLEY GIRL =LIKE GRODY**MAX(FERSURE)**2 THEN FOR I =LIKE 1 TO OH*MAYBE 100 DO*WAH - (DITTY**2); BARF(I)=TOTALLY GROSS(OUT) SURE LIKE, BAG THIS PROGRAM; REALLY; LIKE TOTALLY(Y*KNOW); IM*SURE GOTO THE MALL VALGOL is also characterized by its unfriendly error messages. For example, when the user makes a syntax error, the interpreter displays the message GAG ME WITH A SPOON! A successful compile may be termed MAXIMALLY AWESOME! | |
There's got to be more to life than compile-and-go. | |
If builders built buildings the way programmers write programs, Jolt Cola would be a Fortune-500 company. If builders built buildings the way programmers write programs, you'd be able to buy a nice little colonial split-level at Babbages for $34.95. If programmers wrote programs the way builders build buildings, we'd still be using autocoder and running compile decks. -- Peter da Silva and Karl Lehenbauer, a different perspective | |
"Nuclear war can ruin your whole compile." -- Karl Lehenbauer | |
"Yo, Mike!" "Yeah, Gabe?" "We got a problem down on Earth. In Utah." "I thought you fixed that last century!" "No, no, not that. Someone's found a security problem in the physics program. They're getting energy out of nowhere." "Blessit! Lemme look... <tappity clickity tappity> Hey, it's there all right! OK, just a sec... <tappity clickity tap... save... compile> There, that ought to patch it. Dist it out, wouldja?" -- Cold Fusion, 1989 | |
It's no wonder they call it WinNT; WNT = VMS++; -- Chris Abbey | |
Peace, Love and Compile the kernel... -- Justin L. Herreman | |
Bruno Avila wrote: > I can't find this anywhere. What is the version of the tools to > compile linux kernel 0.0.0.1 (../Historic)? And where can i find them? Well, first you have to find a good source of obsidean, a couple of sharp rocks, and some flint... - Alan Olsen on linux-kernel | |
/* * Check for clue free BIOS implementations who use * the following QA technique * * [ Write BIOS Code ]<------ * | ^ * < Does it Compile >----N-- * |Y ^ * < Does it Boot Win98 >-N-- * |Y * [Ship It] * */ - comment from arch/i386/kernel/dmi_scan.c | |
<Diziet> Fuck, I can't compile the damn thing and I wrote it ! | |
<tigah_-> i have 4gb for /tmp <Knghtbrd> What do you do with 4G /tmp? Compile X? <tigah_-> yes | |
<Mercury> At that point it will compile, but segfault, as it should.. | |
99 little bugs in the code, 99 bugs in the code, fix one bug, compile it again... 101 little bugs in the code.... | |
<mao> why do they insist on ading -Werror... <Misty-chan> Mesa would not compile out of the box if it were done by you guys ;) <knghtbrd> Uh, Mesa DOESN'T compile out of the box most of the time. | |
<Knghtbrd> It is when the example source won't compile ... <``Erik> then you fucked something up <Knghtbrd> Nope, I followed their instructions <``Erik> that may've been your problem :} | |
<calc> Knghtbrd: irc doesn't compile c code very well ;) | |
Once upon a time there was a DOS user who saw Unix, and saw that it was good. After typing cp on his DOS machine at home, he downloaded GNU's unix tools ported to DOS and installed them. He rm'd, cp'd, and mv'd happily for many days, and upon finding elvis, he vi'd and was happy. After a long day at work (on a Unix box) he came home, started editing a file, and couldn't figure out why he couldn't suspend vi (w/ ctrl-z) to do a compile. -- Erik Troan, ewt@tipper.oit.unc.edu | |
Who wants to remember that escape-x-alt-control-left shift-b puts you into super-edit-debug-compile mode? -- Discussion on the intuitiveness of commands, especially Emacs | |
One of the reasons Perl is faster than certain other unnamed interpreted languages is that it binds variable names to a particular package (or scope) at compile time rather than at run time. -- Larry Wall in <199709050035.RAA29328@wall.org> |