The bugs you have to avoid are the ones that give the user not only
"He don't know me vewy well, DO he?" -- Bugs Bunny
If graphics hackers are so smart, why can't they get the bugs out of
There are bugs and then there are bugs. And then there are bugs.
Heuristics are bug ridden by definition. If they didn't have bugs,
Beware of bugs in the above code; I have only proved it correct, not tried it.
Simon stopped listening. He realised he'd had enough. Enough of the theories, enough of the mystery, enough of the bullshit. Enough of the soldiers and guns and MI5. Enough of bugs in phones and in people he cared about. Enough of not being cared about back. Enough of uncertainty and lies and civilisation, collapsing or not. Enough of is part in it, his place, his role; the character of Simon Parfitt and all the baggage it entailed.
Tush! tush! fear boys with bugs.
There are never any bugs you haven't found yet.
The only way for errors to occur in a program is by being put there by the author. No other mechanisms are known. Programs can't acquire bugs by sitting around with other buggy programs.
Testing can show the presense of bugs, but not their absence.
Another effective technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed "Never mind, I see what's wrong. Sorry to bother you." This works remarkably well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor.
"Why waste negative entropy on comments, when you could use the same
Each new user of a new system uncovers a new class of bugs.
The number of computer scientists in a room is inversely proportional
<taniwha> Knghtbrd: we should do a quake episode :knee deep in the code": you run around shooting at bugs:) <Knghtbrd> taniwha: I'll pass the idea on to OpenQuartz ;>
X windows: You'd better sit down. Don't laugh. It could be YOUR thesis project. Why do it right when you can do it wrong? Live the nightmare. Our bugs run faster. When it absolutely, positively HAS to crash overnight. There ARE no rules. You'll wish we were kidding. Everything you never wanted in a window system. And more. Dissatisfaction guaranteed. There's got to be a better way. The next best thing to keypunching. Leave the thrashing to us. We wrote the book on core dumps. Even your dog won't like it. More than enough rope. Garbage at your fingertips. Incompatibility. Shoddiness. Uselessness. X windows.
I just uploaded xtoolplaces-1.6. It fixes all bugs but one: It still coredumps instead of doing something useful. The upstream author's e-mail address bounces, Redhat doesn't provide it and I never used it. -- Sven Rudolph <sr1@os.inf.tu-dresden.de>
99 little bugs in the code, 99 bugs in the code, fix one bug, compile it again... 101 little bugs in the code....
>bug, n: An elusive creature living in a program that makes it incorrect. The activity of "debugging", or removing bugs from a program, ends when people get tired of doing it, not when the bugs are removed. -- "Datamation", January 15, 1984
<Knghtbrd> you know, Linux needs a platform game starring Tux <Knghtbrd> kinda Super Marioish, but with Tux and things like little cyber bugs and borgs and that sort of thing ... <Knghtbrd> And you have to jump past billgatus and hit the key to drop him into the lava and then you see some guy that looks like a RMS or someone say "Thank you for rescuing me Tux, but Linus Torvalds is in another castle!"
<Knghtbrd> mariab - don't think Debian hasn't had some very stupid and obvious bugs before <Knghtbrd> of course, we usually fix ours BEFORE we release =D
Charles Briscoe-Smith <cpbs@debian.org>: After all, the gzip package is called `gzip', not `libz-bin'... James Troup <troup@debian.org>: Uh, probably because the gzip binary doesn't come from the non-existent libz package or the existent zlib package. -- debian-bugs-dist
> Also another major deciding factor is availability of source code. > It just gives everybody a warm fuzzy feeling knowing that there is > source code available to the product you are using. It allows everybody > to improve on the product and fix bugs etc. sooner that the author(s) > would get the time/chance to. I think this is one the really BIG reasons for the snowball/onslaught of Linux and the wealth of stuff available that gets enhanced faster than the real vendors can keep up. -- Norman
The bugs you have to avoid are the ones that give the user not only the inclination to get on a plane, but also the time. -- Kay Bostic
<Culus> Saens demonstrates no less than 3 tcp/ip bugs in 2.2.3
"Why waste negative entropy on comments, when you could use the same entropy to create bugs instead?" -- Steve Elias
<jt> should a bug be marked critical if it only affects one arch? <james-workaway> jt: rc for that arch maybe, but those kind of arch specific bugs are rare... <jt> not when it's caused by a bug in gcc <doogie> jt: get gcc removed from that arch. :)
The number of computer scientists in a room is inversely proportional to the number of bugs in their code.
Still a few bugs in the system... Someday I have to tell you about Uncle Nahum from Maine, who spent years trying to cross a jellyfish with a shad so he could breed boneless shad. His experiment backfired too, and he wound up with bony jellyfish... which was hardly worth the trouble. There's very little call for those up there. -- Allucquere R. "Sandy" Stone
<jim> Lemme make sure I'm not wasting time here... bcwhite will remove pkgs that havent been fixed that have outstanding bugs of severity "important". True or false? <JHM> jim: "important" or higher. True. <jim> Then we're about to lose ftp.debian.org and dpkg :) * netgod will miss dpkg -- it was occasionally useful <Joey> We still have rpm.... -- Seen on #Debian
It hangs down from the chandelier Nobody knows quite what it does Its color is odd and its shape is weird It emits a high-sounding buzz It grows a couple of feet each day and wriggles with sort of a twitch Nobody bugs it 'cause it comes from a visiting uncle who's rich! -- To "It Came Upon A Midnight Clear"
Eleanor Rigby Sits at the keyboard And waits for a line on the screen Lives in a dream Waits for a signal Finding some code That will make the machine do some more. What is it for? All the lonely users, where do they all come from? All the lonely users, why does it take so long? Hacker MacKensie Writing the code for a program that no one will run It's nearly done Look at him working, fixing the bugs in the night when there's nobody there. What does he care? All the lonely users, where do they all come from? All the lonely users, why does it take so long? Ah, look at all the lonely users. Ah, look at all the lonely users.
>Bugs, pl. n.: Small living things that small living boys throw on small living girls.
<doogie> dpkg has bugs? no way!
<stu> apt: !bugs</p> <apt> !bugs are stupid <dpkg> apt: are stupid? what's that? <apt> dpkg: i don't know <dpkg> apt: Beauty is in the eye of the beer holder... <apt> i already had it that way, dpkg.
Also another major deciding factor is availability of source code. It just gives everybody a warm fuzzy feeling knowing that there is source code available to the product you are using. It allows everybody to improve on the product and fix bugs etc. sooner that the author(s) would get the time/chance to. -- Atif Khan
The wise programmer is told about the Tao and follows it. The average programmer is told about the Tao and searches for it. The foolish programmer is told about the Tao and laughs at it. If it were not for laughter, there would be no Tao. The highest sounds are the hardest to hear. Going forward is a way to retreat. Greater talent shows itself late in life. Even a perfect program still has bugs. -- Geoffrey James, "The Tao of Programming"
Nobody shot me. -- Frank Gusenberg, his last words, when asked by police who had shot him 14 times with a machine gun in the Saint Valentine's Day Massacre. Only Capone kills like that. -- George "Bugs" Moran, on the Saint Valentine's Day Massacre The only man who kills like that is Bugs Moran. -- Al Capone, on the Saint Valentine's Day Massacre
Acceptance testing: An unsuccessful attempt to find bugs.
If you remove stricture from a large Perl program currently, you're just installing delayed bugs, whereas with this feature, you're installing an instant bug that's easily fixed. Whoopee. -- Larry Wall in <199710050130.SAA04762@wall.org>
Each new user of a new system uncovers a new class of bugs. -- Kernighan
There are never any bugs you haven't found yet.
As long as there are ill-defined goals, bizarre bugs, and unrealistic schedules, there will be Real Programmers willing to jump in and Solve The Problem, saving the documentation for later.
<jim> Lemme make sure I'm not wasting time here... bcwhite will remove pkgs that havent been fixed that have outstanding bugs of severity "important". True or false? <JHM> jim: "important" or higher. True. <jim> Then we're about to lose ftp.debian.org and dpkg :) * netgod will miss dpkg -- it was occasionally useful <Joey> We still have rpm....
"Would I turn on the gas if my pal Mugsy were in there?" "You might, rabbit, you might!" -- Looney Tunes, Bugs and Thugs (1954, Friz Freleng)
Oh, and this is another kernel in that great and venerable "BugFree(tm)" series of kernels. So be not afraid of bugs, but go out in the streets and deliver this message of joy to the masses. -- Linus, in the announcement for 1.3.27
Ever wondered about the origins of the term "bugs" as applied to computer technology? U.S. Navy Capt. Grace Murray Hopper has firsthand explanation. The 74-year-old captain, who is still on active duty, was a pioneer in computer technology during World War II. At the C.W. Post Center of Long Island University, Hopper told a group of Long Island public school adminis- trators that the first computer "bug" was a real bug--a moth. At Harvard one August night in 1945, Hopper and her associates were working on the "granddaddy" of modern computers, the Mark I. "Things were going badly; there was something wrong in one of the circuits of the long glass-enclosed computer," she said. "Finally, someone located the trouble spot and, using ordinary tweezers, removed the problem, a two-inch moth. From then on, when anything went wrong with a computer, we said it had bugs in it." Hopper said that when the veracity of her story was questioned recently, "I referred them to my 1945 log book, now in the collection of the Naval Surface Weapons Center, and they found the remains of that moth taped to the page in question." [actually, the term "bug" had even earlier usage in regard to problems with radio hardware. Ed.]
If graphics hackers are so smart, why can't they get the bugs out of fresh paint?
Class, that's the only thing that counts in life. Class. Without class and style, a man's a bum; he might as well be dead. -- "Bugsy" Siegel
Hacker's Guide To Cooking: 2 pkg. cream cheese (the mushy white stuff in silver wrappings that doesn't really come from Philadelphia after all; anyway, about 16 oz.) 1 tsp. vanilla extract (which is more alcohol than vanilla and pretty strong so this part you *GOTTA* measure) 1/4 cup sugar (but honey works fine too) 8 oz. Cool Whip (the fluffy stuff devoid of nutritional value that you can squirt all over your friends and lick off...) "Blend all together until creamy with no lumps." This is where you get to join(1) all the raw data in a big buffer and then filter it through merge(1m) with the -thick option, I mean, it starts out ultra lumpy and icky looking and you have to work hard to mix it. Try an electric beater if you have a cat(1) that can climb wall(1s) to lick it off the ceiling(3m). "Pour into a graham cracker crust..." Aha, the BUGS section at last. You just happened to have a GCC sitting around under /etc/food, right? If not, don't panic(8), merely crumble a rand(3m) handful of innocent GCs into a suitable tempfile and mix in some melted butter. "...and refrigerate for an hour." Leave the recipe's stdout in a fridge for 3.6E6 milliseconds while you work on cleaning up stderr, and by time out your cheesecake will be ready for stdin.
<zarkov> "NT 5.0. All the bugs and ten times the code size!"
"He don't know me vewy well, DO he?" -- Bugs Bunny
Hack placidly amidst the noisy printers and remember what prizes there may be in Science. As fast as possible get a good terminal on a good system. Enter your data clearly but always encrypt your results. And listen to others, even the dull and ignorant, for they may be your customers. Avoid loud and aggressive persons, for they are sales reps. If you compare your outputs with those of others, you may be surprised, for always there will be greater and lesser numbers than you have crunched. Keep others interested in your career, and try not to fumble; it can be a real hassle and could change your fortunes in time. Exercise system control in your experiments, for the world is full of >bugs. But let this not blind you to what virtue there is; many persons strive for linearity and everywhere papers are full of approximations. Strive for proportionality. Especially, do not faint when it occurs. Neither be cyclical about results; for in the face of all data analysis it is sure to be noticed. Take with a grain of salt the anomalous data points. Gracefully pass them on to the youth at the next desk. Nurture some mutual funds to shield you in times of sudden layoffs. But do not distress yourself with imaginings -- the real bugs are enough to screw you badly. Murphy's Law runs the Universe -- and whether or not it is clear to you, no doubt <Curl>B*n dS = 0. Therefore, grab for a piece of the pie, with whatever proposals you can conceive of to try. With all the crashed disks, skewed data, and broken line printers, you can still have a beautiful secretary. Be linear. Strive to stay employed. -- Technolorata, "Analog"
"We don't do a new version to fix bugs." - Bill Gates "The new version - it's not there to fix bugs." - Bill Gates -- Retranslated from Focus 43/1995, pp. 206-212
Heuristics are bug ridden by definition. If they didn't have bugs, then they'd be algorithms.
A newspaper is a circulating library with high blood pressure. -- Arthure "Bugs" Baer
As I was passing Project MAC, I met a Quux with seven hacks. Every hack had seven bugs; Every bug had seven manifestations; Every manifestation had seven symptoms. Symptoms, manifestations, bugs, and hacks, How many losses at Project MAC?
<hoponpop> my program works if i take out the bugs.
Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald Knuth
There are bugs and then there are bugs. And then there are bugs. -- Karl Lehenbauer
After sifting through the overwritten remaining blocks of Luke's home directory, Luke and PDP-1 sped away from /u/lars, across the surface of the Winchester riding Luke's flying read/write head. PDP-1 had Luke stop at the edge of the cylinder overlooking /usr/spool/uucp. "Unix-to-Unix Copy Program;" said PDP-1. "You will never find a more wretched hive of bugs and flamers. We must be cautious." -- DECWARS
Testing can show the presense of bugs, but not their absence. -- Dijkstra
Next came the account of Mitya's sudden determination to "step aside" and make way for their happiness. But he could not make up his mind to open his heart to them as before, and tell them about "the queen of his soul." He disliked speaking of her before these chilly persons "who were fastening on him like bugs." And so in response to their reiterated questions he answered briefly and abruptly:
But it warn't. It was Jack-o'-lanterns, or lightning bugs; so he set down again, and went to watching, same as before. Jim said it made him all over trembly and feverish to be so close to freedom. Well, I can tell you it made me all over trembly and feverish, too, to hear him, because I begun to get it through my head that he _was_ most freeand who was to blame for it? Why, _me_. I couldn't get that out of my conscience, no how nor no way. It got to troubling me so I couldn't rest; I couldn't stay still in one place. It hadn't ever come home to me before, what this thing was that I was doing. But now it did; and it stayed with me, and scorched me more and more. I tried to make out to myself that I warn't to blame, because I didn't run Jim off from his rightful owner; but it warn't no use, conscience up and says, every time, "But you knowed he was running for his freedom, and you could a paddled ashore and told somebody." That was soI couldn't get around that noway. That was where it pinched. Conscience says to me, "What had poor Miss Watson done to you that you could see her nigger go off right under your eyes and never say one single word? What did that poor old woman do to you that you could treat her so mean? Why, she tried to learn you your book, she tried to learn you your manners, she tried to be good to you every way she knowed how. _That's_ what she done."
WHEN I got there it was all still and Sunday-like, and hot and sunshiny; the hands was gone to the fields; and there was them kind of faint dronings of bugs and flies in the air that makes it seem so lonesome and like everybody's dead and gone; and if a breeze fans along and quivers the leaves it makes you feel mournful, because you feel like it's spirits whisperingspirits that's been dead ever so many yearsand you always think they're talking about _you_. As a general thing it makes a body wish _he_ was dead, too, and done with it all.
After hatching or birth an insect undergoes a process of growth and change until the adult condition is reached. The varied details of this post-embryonic development furnish some of the most interesting facts and problems to the students of the Hexapoda. Wingless insects, such as spring-tails and lice, make their appearance in the form of miniature adults. Some winged insects--cockroaches, bugs (fig. 20) and earwigs, for example--when young closely resemble their parents, except for the absence of wings. On the other hand, we find in the vast majority of the Hexapoda a very marked difference between the perfect insect (imago) and the young animal when newly hatched and for some time after hatching. From the moth's egg comes a crawling caterpillar (fig. 21, c), from the fly's a legless maggot (fig. 25, a). Such a young insect is a _larva_--a term used by zoologists for young animals generally that are decidedly unlike their parents. It is obvious that the hatching of the young as a larva necessitates a more or less profound transformation or metamorphosis before the perfect state is attained. Usually this transformation comes with apparent suddenness, at the penultimate stage of the insect's life-history, when the passive pupa (fig. 21, d) is revealed, exhibiting the wings and other imaginal structures, which have been developed unseen beneath the cuticle of the larva. Hexapoda with this resting pupal stage in their life-history are said to undergo "a complete transformation," to be metabolic, or holometabolic, whereas those insects in which the young form resembles the parent are said to be ametabolic. Such insects as dragon-flies and may-flies, whose young, though unlike the parent, develop into the adult form without a resting pupal stage are said to undergo an "incomplete transformation" or to be hemimetabolic. The absence of the pupal stage depends upon the fact that in the ametabolic and hemimetabolic Hexapoda the wing-rudiments appear as lateral outgrowths (fig. 22) of the two hinder thoracic segments and are visible externally throughout the life-history, becoming larger after each moult or casting of the cuticle. Hence, as has been pointed out by D. Sharp (1898), the marked divergence among the Hexapoda, as regards life-history, is between insects whose wings develop outside the cuticle (Exopterygota) and those whose wings develop inside the cuticle (Endopterygota), becoming visible only when the casting of the last larval cuticle reveals the pupa. Metamorphosis among the Hexapoda depends upon the universal acquisition of wings during post-embryonic development--no insect being hatched with the smallest external rudiments of those organs--and on the necessity for successive castings or "moults" (ecdyses) of the cuticle. Entry: FIG