PROGRAMMER JOKES AND CHUTKULE

Hello

Shooting yourself in the foot in various programming languages :

370 jcl
- you send your foot down to mis and include a 300-page document explaining exactly how you want it to be shot. two years later, your foot comes back deep-fried.
- you shoot yourself in the head just thinking about it.
- you find the first building you're in in the phone book, then find your office number in the corporate phone book. then you have to write this down and describe, in cubits, your exact location in relation to the door (the right side thereof). then you need to write down the location of the gun (loading it is a proprietary utility), then you load it, and the cobol program, and run them, and with luck, it may be run tonight.

Ada
- if you are dumb enough to actually use this language, the united states department of defense will kidnap you, stand you up in front of a firing squad, and tell the soldiers, "shoot at his feet."
- after correctly packaging your foot, you attempt to concurrently load the gun, pull the trigger, scream, and shoot yourself in the foot. when you try, however, you discover that your foot is of the wrong type.
- you scour all 156e54 pages of the manuals, looking for references to foot, leg, or toe; then you get hopelessly confused and give up. you sneak in when the boss isn't around and finally write the damn thing in c. you turn in 7,689 pages of source code to the review committee, knowing they'll never look at it, and when the program needs maintenance, you quit.

Algol
- you shoot yourself in the foot with a civil war-era musket. the musket is aesthetically fascinating, and the wound baffles the adolescent medic in the emergency room.

Algol 60
- you spend hours trying to figure out how to fire the gun because it has no provisions for input or output.

Algol 68
- you mildly deprocedure the gun, the bullet gets firmly dereferenced, and your foot is strongly coerced to void.

Apl
- you shoot yourself in the foot and then spend all day figuring out how to do it in fewer characters.
- you hear a gunshot and there's a hole in your foot, but you don't remember enough linear algebra to understand what happened.
- @#&^$%&%^ foot

Apt
- you cut a perfect bullet hole in your foot and shoot through it.

Asp
- you try to shoot yourself in the foot, but the most advanced thing you can manage is to cut your wrist.

Assembly
- you try to shoot yourself in the foot only to discover that you must first invent the gun, the bullet, the trigger, and your foot.
- you crash the os and overwrite the root disk. the system administrator arrives and shoots you in the foot. after a moment of contemplation, the system administrator shoots himself in the foot and then hops around the room rapidly shooting at everyone in sight.
- by the time you've written the gun, you are dead, and don't have to worry about shooting your feet. alternatively, you shoot and miss, but don't notice.
- using only 7 bytes of code, you blow off your entire leg in only 2 cpu clock ticks.

Basic
- shoot self in foot with water pistol. on big systems, continue until entire lower body is waterlogged.

Bcpl
- you shoot yourself somewhere in the leg; you can't get any finer resolution than that.

C
- you shoot yourself in the foot.
- you shoot yourself in the foot and then nobody else can figure out what you did.

C++
- you accidentally create a dozen instances of yourself and shoot them all in the foot. providing emergency medical assistance is impossible since you can't tell which are bitwise copies and which are just pointing at others and saying, "that's me, over there."

C#
- you shoot yourself in the foot, but first have to switch to unsafe mode.
- you forget precisely how to use the .net interface and shoot yourself in the foot. you sue microsoft for damages.

Cobol
- useing a colt.45 handgun, aim gun at leg.foot, then place arm.hand.finger on handgun.trigger and squeeze. then return handgun to holster. check whether shoelace needs to be retied.
- allocate $500,000 for the project. define foot, bullet, gun. run press_trigger. go for coffee break. return in time to put foot under bullet.
- you try to shoot yourself in the foot, but the gun won't fire unless it's aligned in column 8.

Css
- everyone can now shoot themselves in the foot, but all their feet come out looking identical and attached to their ears.

Dcl
$ mount/density=.45/label=bullet/message="bye" bullet::bullet$gun sys$bullet
$ set gun/load/safety=off/sight=none/hand=left/chamber=1/action=automatic/log/all/gull sys$gun_3$dua3:[000000] gun.gun
$ shoot/log/auto sys$gun sys$system:[foot] foot.foot
%dcl-w-actimage, error activating image gun
-cli-e-imgname image file $3$dua240:[gun] gun.exe;1
-imgact-f-notnative, image is not an openvms alpha axp image

Delphi
- you try to shoot yourself in the foot but discover that the bullets you already had are not compatible with the new gun version, but borland promises a fix real soon now.

Eiffel
- you create a gun object, two foot objects, and a bullet object. the gun passes both the foot objects as a reference to the bullet. the foot objects increment their hole counts and forget about the bullet. a little demon then drives a garbage truck over your feet and grabs the bullet (both of it) on the way.
- you take out a contract on your foot. the precondition is that there's a bullet in the gun; the postcondition is that there's a hole in your foot.

Forth
- foot in yourself shoot.
- first you decide to leave the number of toes lost on the stack and then implement the word foot-toes@ which takes three numbers from the stack: foot number, range, and projectile mass (in slugs) and changes the current vocabulary to blue. while testing this word you are arrested by the police for mooning (remember, this is a bottom-up language) who demonstrate the far better top-down approach to damaging yourself.
- bullet dup3 * gun load foot aim trigger pull bang emit dead if drop rot then. this takes about five bytes of memory, executes in two to ten clock cycles on any processor, and can be used to replace any existing function of the language as well as in any future words. welcome to bottom-up programming, where you too can perform compiler pre-processing instead of actually writing code.

Fortran
- you shoot yourself in each toe, iteratively, until you run out of toes, then you read in the next foot and repeat. if you run out of bullets or toes, you continue anyway because no excepti
On processing was anticipated.

Haskell
- on a warm saturday afternoon, sitting by the pool with a margarita, you casually sit up from your chaise lounge chair, reach over and pick up a gun, aim at your foot, and lazily pull the trigger.
- you shoot yourself in the foot very elegantly, and wonder why the whole world isn't shooting itself this way.
- you spend several hours creating a new copy of the universe which is identical to the existing one except your foot has a hole in it. you then hear that it can be done more elegantly with dyadic functile hyper-arrows, but the very act of reading some of the included sample code causes one of your metatarsals to explode.

Html
- you cut a bullethole in your foot with nothing more than a small penknife, but you realize that to make it look convincing, you need to be using dreamweaver.

Hypertalk
- put the first bullet of the gun into foot left of leg of you. answer the result.
- you describe how to shoot yourself in the foot, which not only happens, but you also get cool visual effects.
- as of hypertalk 2.2, you cannot shoot yourself in the foot from within the stack; you must write this functionality into an xcmd or xfcn. however, we anticipate this functionality to be incorporated into the next major release.

Idl
- you easily shoot yourself in the foot, complete with neat little graphs showing the trajectory of the bullet and the result of the impact. after twenty hours and ten thousand lines of code, your friend proudly announces that he has accomplished the same thing in an excel spreadsheet.

Java
- you write a program to shoot yourself in the foot and put it on the internet. people all over the world shoot themselves in the foot, and everyone leaves your website hobbling and cursing.
- you amputate your foot at the ankle with a fourteen-pound hacksaw, but you can do it on any platform.

Javascript
- you find that microsoft and sun have released incompatible class libraries both implementing gun objects. you then find that although there are plenty of foot objects implemented in the past in many other languages, you cannot get access to one. but, seeing as javascript is so cool, you don't care and go around shooting anything else you can find.

Latex
compy$ more foot_shooting.tex

documentclass[12pt]{article}
usepackage{latexgun,latexshoot}
egin{document}
see how easy it is to shoot yourself in the foot?
gun[leftfoot]{shoot}
pain
end{document}

compy$ latex foot_shooting
...
line 6: undefined control sequence pain

Lisp
- you shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds the gun with which you shoot...
- you attempt to shoot yourself in the foot, but the gun jams on a stray parenthesis.

Modula-2
- after realizing that you can't actually accomplish anything in the language, you shoot yourself in the head.

Moo
- you ask a wizard for a pair of hands. after lovingly hand-crafting the generic gun and generic bullet, you flag the objects as fertile and then tell everyone they can now shoot themselves in the foot.

Motif
- you spend days writing a uil description of your foot, the trajectory, the bullet, and the intricate scrollwork on the ivory handles of the gun. when you finally get around to pulling the trigger, the gun jams.

Ms-dos
- you finally find the gun, but you can't find the file with the bullets for the life of you.
- you shoot yourself in the foot, but you can unshoot yourself with add-on software.

Mpw
- because you don't actually have a gun, you write an imitation unix shell and shoot yourself in the foot using pascal.

.net
- you can now shoot yourself in the foot with any of fourteen weapons, ranging from an antique medieval crossbow to a laser-guided destructo-beam. however, all these weapons must be manufactured by microsoft and you must pay microsoft royalties every time you shoot yourself in the foot.

Objective-c
- you write a protocol for shooting yourself in the foot so that all people can get shot in their feet.

Oracle
- you decide to shoot yourself in the foot, so you go out and buy a gun, but the gun won't work without "deploying" a shoulder holster solution, relational titanium-alloy bullets, body armor infrastructure, a laser sight assistant, a retractable arm stock application, and an enterprise team of ballistic experts and a chiropodist.
- the menus for coding foot_shooting have not been implemented yet, and you can't do foot_shooting in sql.

Pascal
- the compiler won't let you shoot yourself in the foot.
- the gun is mounted such that it cannot point towards your feet, but you can swivel it round and shoot yourself in the head instead.

Perl
- you separate the bullet from the gun with a hyperoptimized regexp, and then you transport it to your foot using several typeglobs. however, the program fails to run and you can't correct it since you don't understand what the hell it is you've written.
- you stab yourself in the foot repeatedly with an incredibly large and very heavy swiss army knife.
- you shoot yourself in the foot and then decide it was so much fun that you invent another six completely different ways to do it.
- there are so many ways to shoot yourself in the foot that you post a query to comp.lang.perl.misc to determine the optimal approach. after sifting through 500 replies (which you accomplish with a short perl script), not to mention the cross-posts to the perl5-porters mailing list for which you upgraded your first sifter into a package, which of course you uploaded to cpan for others who might have a similar problem (which, of course, is the problem of sorting out e-mail and news, not the problem of shooting yourself in the foot), you set to the task of simply and elegantly shooting yourself in the foot, until you discover that, while it works fine in most cases, nt, vms, and various flavors of linux, aix, and irix all let you shoot you in the foot sooner than your perl script could.

Php
- three thousand people line up on your apartment's welcome mat and demand to be shot in their feet. one by one, you oblige them, but halfway through, the http connection times out and the crowd lynches you.

Pl/1
- after consuming all system resources including bullets, the data processing department doubles its size, acquires two new mainframes, and drops the original on your foot.

Postscript
- foot bullets 6 locate loadgun aimgun shoot showpage

Prolog
- you tell your program you wish to be shot in the foot. the program figures out how to do it, but the syntax doesn't allow it to explain.
- your program tries to shoot you in the foot, but you die of old age before the bullet leaves the gun.

Python
- you shoot yourself in the foot and then brag for hours about how much more elegantly you did it than if you had been using c or (god forbid) perl.
- you create a gun module, a gun class, a foot module, and a foot class. after realizing you can't point the gun at the foot, you pass a reference to the gun to a foot object. after the foot is blown up, the gun object remains alive for eternity, ready to shoot all future feet that may happen to appear.

Ruby
- you shoot yourself in the foot and then have to justify it to all your friends who are still naively using perl.

Sas
- you spend three hours trying to cut your way through your foot with a rock flake, only to realize that the language was invented before guns allowed you to shoot yourself in the foot interactively in one easy step with no programming.
- you have no idea that the gun, the bullet, or your foot exists. the gun is locked in a safe in a bank vault on the other side of the galaxy, the bullet is locked in a safe in a bank vault in another galaxy, and the people who know the combinations fo
1000
R the safes and bank vaults died ten million years ago. still, the gun goes off and fires the bullet through your foot.

Scheme
- you shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds the gun with which you shoot...but none of the other appendages are aware this is happening.
- you vaguely remember something from your comp sci 101 class about shooting yourself in the foot, but why should you waste your time shooting yourself using a functional programming language?

Sh, csh, etc.
- you can't remember the syntax for anything so you spend five hours reading man pages before giving up. you then shoot the computer and switch to c.

Sml/nj
- you program a structure for your foot, the gun, and the bullet, complete with associated signatures and function definitions. after two hours of laborious typing, forgetting of semicolons, and searching old comp sci textbooks for the definition of such phrases as "polymorphic dynamic objective typing system", as well as an additional hour for brushing up on the lambda calculus, you run the program and the interpreter tells you that the pattern-match between your foot and the bullet is nonexhaustive. you feel a slight tingling pain, but no bullethole appears in your foot because your program did not allow for side-effecting statements.

Snobol
- if you succeed, shoot yourself in the left foot. if you fail, shoot yourself in the right foot.
- you grab your foot with your hand, then rewrite your hand to be a bullet. the act of shooting the original foot then changes your hand/bullet into yet another foot (a left foot).

Sql
- you cut your foot off, send it out to a service bureau, and when it returns it has a hole in it, but it will no longer fit the attachment at the end of your leg.

Visual basic
- you'll only appear to have shot yourself in the foot, but you'll have so much fun doing it you won't care.
- you do a google search on how to shoot yourself in the foot using visual basic. you find seventeen completely different ways to do it, none of which are properly structured. you paste the first example into the ide and compile. it brushes your teeth.

Vms
- %sys-f-ftsht, foot shot (fifty lines of traceback omitted)

Xbase
- shooting yourself is no problem, but if you want to shoot yourself in the foot, you'll have to use clipper.

Xcode
- your objective-c and java programs now have nifty little graphical interfaces and will run on both powerpc and x86-based architectures, but you still can't shoot yourself in the foot unless you're the superuser.

Xml
- you vaporize your entire lower half with a bazooka.
- you can't actually shoot yourself in the foot; all you can do is describe the gun in painful detail.

Z
- you write out all the specification of your foot, the bullet, the gun, and the relevant laws of physics, but all you can do is prove that you can shoot yourself in the foot.

Windows as virus! 1. viruses replicate quickly. windows does this. 2. viruses use up valuable system resources, slowing down t
He system as they do so. windows does this. 3. viruses will, from time to time, trash your hard disk. windows does this. 4. viruses are usually carried, unkown to the user, along with valuable programs and systems. windows does that too. 5. viruses will occasionally make the user suspect their system is too slow and the user will buy new hardware. same with windows, yet again. maybe windows really is a virus. nope! there is a difference! viruses are well supported by their authors, are frequently updated, and tend to become more sophisticated as they mature. so there! windows is not a virus.

A programming team developes true ai capable of thinking, reasoning, and feeling. they wrote all the code
Aaf
in scheme they go to their project manager and tell him of their invention and invite him to come talk to it. he agrees and sits down at the terminal they point to. he types: hello and it replies: (hello) he types: how are you? it replies: ((i'm fine, thanks)(how are you?)) the pm gets up and tells the team he hates the program and that he's ending the project. the team starts pleading with him, asking how he could hate a true ai capable of feelings and reason. they tell him it can think, solve problems, and even work as a member of the team. the pm replies, "yes, but it talks with a lisp."

Electrical engineering vs. computer science once upon a time, in a kingdom not far from here, a king summoned two of his advisors for a test. he showed them both a shiny metal box with two slots in the top, a control knob, and a lever. "what do you think this is?" one advisor, an electrical engineer, answered first. "it is a toaster," he said. the king asked, "how would you design an embedded computer for it?" the advisor: "using a four-bit microcontroller, i would write a simple program that reads the darkness knob and quantifies its position to one of 16 shades of darkness, from snow white to coal black. the program would use that darkness level as the index to a 16-element table of initial timer values. then it would turn on the heating elements and start the timer with the initial value selected from the table. at the end of the time delay, it would turn off the heat and pop up the toast. come back next week, and i'll show you a working prototype." the second advisor, a software developer, immediately recognized the danger of such short-sighted thinking. he said, "toasters don't just turn bread into toast, they are also used to warm frozen waffles. what you see before you is really a breakfast food cooker. as the subjects of your kingdom become more sophisticated, they will demand more capabilities. they will need a breakfast food cooker that can also cook sausage, fry bacon, and make scrambled eggs. a toaster that only makes toast will soon be obsolete. if we don't look to the future, we will have to completely redesign the toaster in just a few years." "with this in mind, we can formulate a more intelligent solut
C54
Ion to the problem. first, create a class of breakfast foods. specialize this class into subclasses: grains, pork, and poultry. the specialization process should be repeated with grains divided into toast, muffins, pancakes, and waffles; pork divided into sausage, links, and bacon; and poultry divided into scrambled eggs, hard- boiled eggs, poached eggs, fried eggs, and various omelette classes." "the ham and cheese omelette class is worth special attention because it must inherit characteristics from the pork, dairy, and poultry classes. thus, we see that the problem cannot be properly solved without multiple inheritance. at run time, the program must create the proper object and send a message to the object that says, 'cook yourself.' the semantics of this message depend, of course, on the kind of object, so they have a different meaning to a piece of toast than to scrambled eggs." "reviewing the process so far, we see that the analysis phase has revealed that the primary requirement is to cook any kind of breakfast food. in the design phase, we have discovered some derived requirements. specifically, we need an object-oriented language with multiple inheritance. of course, users don't want the eggs to get cold while the bacon is frying, so concurrent processing is required, too." "we must not forget the user interface. the lever that lowers the food lacks versatility, and the darkness knob is confusing. users won't buy the product unless it has a user-friendly, graphical interface. when the breakfast cooker is plugged in, users should see a cowboy boot on the screen. users click on it, and the message 'booting unix v.8.3' appears on the screen. (unix 8.3 should be out by the time the product gets to the market.) users can pull down a menu and click on the foods they want to cook." "having made the wise decision of specifying the software first in the design phase, all that remains is to pick an adequate hardware platform for the implementation phase. an intel pentium with 48mb of memory, a 1.2gb hard disk, and a svga monitor should be sufficient. if you select a multitasking, object oriented language that supports multiple inheritance and has a built-in gui, writing the program will be a snap." the king wisely had the software developer beheaded, and they all lived happily ever after.