Dictionary De - En
De - Es
De - Pt| Proverbs, aphorisms, quotations (English) | by Linux fortune |
| === ALL CSH USERS PLEASE NOTE ======================== Set the variable $LOSERS to all the people that you think are losers. This will cause all said losers to have the variable $PEOPLE-WHO-THINK-I-AM-A-LOSER updated in their .login file. Should you attempt to execute a job on a machine with poor response time and a machine on your local net is currently populated by losers, that machine will be freed up for your job through a cold boot process. | |
| === ALL USERS PLEASE NOTE ======================== The garbage collector now works. In addition a new, experimental garbage collection algorithm has been installed. With SI:%DSK-GC-QLX-BITS set to 17, (NOT the default) the old garbage collection algorithm remains in force; when virtual storage is filled, the machine cold boots itself. With SI:%DSK-GC- QLX-BITS set to 23, the new garbage collector is enabled. Unlike most garbage collectors, the new gc starts its mark phase from the mind of the user, rather than from the obarray. This allows the garbage collection of significantly more Qs. As the garbage collector runs, it may ask you something like "Do you remember what SI:RDTBL-TRANS does?", and if you can't give a reasonable answer in thirty seconds, the symbol becomes a candidate for GCing. The variable SI:%GC-QLX-LUSER-TM governs how long the GC waits before timing out the user. | |
| As Will Rogers would have said, "There is no such things as a free variable." | |
| I'm a Lisp variable -- bind me! | |
| Proposed Additions to the PDP-11 Instruction Set: PI Punch Invalid POPI Punch Operator Immediately PVLC Punch Variable Length Card RASC Read And Shred Card RPM Read Programmers Mind RSSC reduce speed, step carefully (for improved accuracy) RTAB Rewind tape and break RWDSK rewind disk RWOC Read Writing On Card SCRBL scribble to disk - faster than a write SLC Search for Lost Chord SPSW Scramble Program Status Word SRSD Seek Record and Scar Disk STROM Store in Read Only Memory TDB Transfer and Drop Bit WBT Water Binary Tree | |
| Speaking as someone who has delved into the intricacies of PL/I, I am sure that only Real Men could have written such a machine-hogging, cycle-grabbing, all-encompassing monster. Allocate an array and free the middle third? Sure! Why not? Multiply a character string times a bit string and assign the result to a float decimal? Go ahead! Free a controlled variable procedure parameter and reallocate it before passing it back? Overlay three different types of variable on the same memory location? Anything you say! Write a recursive macro? Well, no, but Real Men use rescan. How could a language so obviously designed and written by Real Men not be intended for Real Man use? | |
| The primary purpose of the DATA statement is to give names to constants; instead of referring to pi as 3.141592653589793 at every appearance, the variable PI can be given that value with a DATA statement and used instead of the longer form of the constant. This also simplifies modifying the program, should the value of pi change. -- FORTRAN manual for Xerox Computers | |
| FORTRAN? The syntactically incorrect statement "DO 10 I = 1.10" will parse and generate code creating a variable, DO10I, as follows: "DO10I = 1.10" If that doesn't terrify you, it should. | |
| curtation, n.: The enforced compression of a string in the fixed-length field environment. The problem of fitting extremely variable-length strings such as names, addresses, and item descriptions into fixed-length records is no trivial matter. Neglect of the subtle art of curtation has probably alienated more people than any other aspect of data processing. You order Mozart's "Don Giovanni" from your record club, and they invoice you $24.95 for MOZ DONG. The witless mapping of the sublime onto the ridiculous! Equally puzzling is the curtation that produces the same eight characters, THE BEST, whether you order "The Best of Wagner", "The Best of Schubert", or "The Best of the Turds". Similarly, wine lovers buying from computerized wineries twirl their glasses, check their delivery notes, and inform their friends, "A rather innocent, possibly overtruncated CAB SAUV 69 TAL." The squeezing of fruit into 10 columns has yielded such memorable obscenities as COX OR PIP. The examples cited are real, and the curtational methodology which produced them is still with us. MOZ DONG n. Curtation of Don Giovanni by Wolfgang Amadeus Mozart and Lorenzo da Ponte, as performed by the computerized billing ensemble of the Internat'l Preview Society, Great Neck (sic), N.Y. -- Stan Kelly-Bootle, "The Devil's DP Dictionary" | |
| One man's constant is another man's variable. -- A.J. Perlis | |
| I've built a better model than the one at Data General For data bases vegetable, animal, and mineral My OS handles CPUs with multiplexed duality; My PL/1 compiler shows impressive functionality. My storage system's better than magnetic core polarity, You never have to bother checking out a bit for parity; There isn't any reason to install non-static floor matting; My disk drive has capacity for variable formatting. I feel compelled to mention what I know to be a gloating point: There's lots of room in memory for variables floating-point, Which shows for input vegetable, animal, and mineral I've built a better model than the one at Data General. -- Steve Levine, "A Computer Song" (To the tune of "Modern Major General", from "Pirates of Penzance", by Gilbert & Sullivan) | |
| Unobfuscated Perl (#2) A rogue group of Perl hackers has presented a plan to add a "use really_goddamn_strict" pragma that would enforce readability and UNobfuscation. With this pragma in force, the Perl compiler might say: * Warning: Write-only code detected between lines 612 and 734. While this code is perfectly legal, you won't have any clue what it does in two weeks. I recommend you start over. * Warning: Code at line 1,024 is indistinguishable from line noise or the output of /dev/random * Warning: Have you ever properly indented a piece of code in your entire life? Evidently not. * Warning: I think you can come up with a more descriptive variable name than "foo" at line 1,523. * Warning: Programmer attempting to re-invent the wheel at line 2,231. There's a function that does the exact same thing on CPAN -- and it actually works. | |
| > valerie kernel: mtrr: your CPUs had inconsistent variable MTRR settings > valerie kernel: mtrr: probably your BIOS does not setup all CPUs It indicates your bios authors can't read standards. Thats a quite normal state of affairs, so common that the kernel cleans up after them - Alan Cox on linux-kernel | |
| * Knghtbrd assigns 3 to Chris * variable wonders who else is named chris besides me <Knghtbrd> variable - you. => * Knghtbrd waits for variable to dramatically say "I feel SO used!" <variable> Knghtbrd: :) * variable ++ <variable> :) | |
| The questions remain the same. The answers are eternally variable. | |
| 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> | |
| You tell it that it's indicative by appending $!. That's why we made $! such a short variable name, after all. :-) -- Larry Wall in <199709081801.LAA20629@wall.org> | |
