PDA

View Full Version : Programming Puns



kermi3
03-18-2002, 10:05 PM
If you put a Unix shell to your ear, will you hear the C?

...add your puns...

doubleanti
03-18-2002, 10:29 PM
this isn't a pun but i thought it was funny...

i don't think therefore i am confused...

kermi3
03-18-2002, 11:14 PM
fine then add your regular programming jokes to ;)

doubleanti
03-18-2002, 11:20 PM
okay! now we're talkin'!!!

if debugging is the process of removing bugs, then programming must be the process of putting them in...

[not myne heard somewhere...]

Yoshi
03-18-2002, 11:42 PM
Debugging is a process to create more bugs.
I program the program using a program to program the program.

nvoigt
03-19-2002, 02:14 AM
Shift to the left! Shift to the right! Pop up, push down, byte, byte, byte!

BREAKFAST.COM Halted...Cereal Port Not Responding.

Salmon Day:
The experience of spending an entire day swimming upstream only to get screwed in the end.

What do Unix sysadmins do when they're horny?
Mount a filesystem.


And my personal all-time favorite: ( ->RTFM )

Why is "256 Ways To Make Love" the most quoted book on the Internet?
It is the f***ing Manual.

ober
03-19-2002, 08:32 AM
>>And my personal all-time favorite: ( ->RTFM )

>Why is "256 Ways To Make Love" the most quoted book on the Internet?
It is the ****ing Manual.

LMAO... that's a good one... haven't heard that before...

Brian
03-19-2002, 12:00 PM
I live by the Tao.
http://www.users.cloud9.net/~hennessy/tao.html

RobR
03-19-2002, 12:11 PM
I once walked in on a friend who was hammering away on his keyboard as hard as he could. I asked him what he was doing, and he replied programming.

When I aked why he was hitting the keys so hard, he replied

"Don't you know that C++is strongly typed"

Ha Ha Ha Ha!!!

RobR
03-19-2002, 12:21 PM
I used to design my functions to be portable....... but I found it caused too many arguments.

Brian
03-19-2002, 12:23 PM
I used to be a very BASIC programmer, but now I C the light.

incognito
03-19-2002, 03:03 PM
DRUG DEALERS & SOFTWARE ENGINEERS-COMPARISON

Drug Dealers

"The first one is free"
*Have important South-Asia connections (to help move the stuff)
*Strange jargon: "Stick", "Rock", "Dime bag", "E"
*Realize that there's a ton of cash in the 14- to 25-year-old market
*Job is assisted by industry's producing newer, more potent mixes
*Often seen in the company of pimps and hustlers
*Their products cause unhealthy addictions.
*Do your job well and you can sleep with sexy movie stars who depend on you


Software Enginners

*"Download a free trial version"
*Have important South-Asia connections (to help debug the code)
*Strange jargon: "TCP/IP", "XML", "Java", "SQL"
*Realize that there's a ton of cash in the 14- to 25-year-old market
*Job is assisted by industry's producing newer, faster machines
*Often seen in the company of marketing people and venture capitalists
*DOOM. Quake. SimCity. Duke Nukem 3D.; Enough said.
*Damn! Damn! DAMN!

ober
03-19-2002, 03:11 PM
LMAO... good one... :D

incognito
03-19-2002, 03:12 PM
found that one on a website once and I liked it so much I decided to save it :D

DavidP
03-19-2002, 03:35 PM
PROGRAMMING CONTEST BETWEEN JESUS AND SATIN

One day God decided he wanted to have a programming contest between Jesus and Satin. So he set them up at their computers, gave them their programming problems which they had to solve, and let them go at it.

An hour or so went by, and they were still programming away, solving each problem one by one.

Suddenly the power went out for a couple seconds and then came back on, making them lose whatever they were working on.

God said, "Jesus wins."

Satan stood up in protest. "Why? How did he win! I lost all my work when the power went out!"

God replied, "Jesus saves."

incognito
03-19-2002, 03:37 PM
The boy is smoking and leaving smoke rings into the air.
The girl gets irritated with the smoke and says to her lover: "Can't you see the warning written on the cigarettes packet, smoking is injurious to health!"
The boy replies back: "Darling, I am a programmer. We don't worry about warnings, we only worry about errors."

Prelude
03-19-2002, 04:27 PM
Instruction to "Enforce In-Order Execution of I/O", known affectionately as E.I.E.I.O.

If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one?
/* A special reward goes to the first person who can actually answer this */

-Prelude

Unregistered
03-19-2002, 04:29 PM
a protected abstract virtual base pure virtual private destructor is a function that:
can only be called by members or friends of that class, and
has no definition in the base class that declares it, but will be defined later in a derived class,
that (refering to the derived class) shares the multiply inherited base,
which (refering to the base class) is inherited in a protected way.

Barjor
03-19-2002, 04:29 PM
I know that one..To bad I don't know the english word for it. /*BUMMER no reward.*/

RobR
03-19-2002, 04:32 PM
Bummer. Just my luck to know the answer <grin> and I get logged out (see above)

a protected abstract virtual base pure virtual private destructor is a function that:
can only be called by members or friends of that class, and
has no definition in the base class that declares it, but will be defined later in a derived class,
that (refering to the derived class) shares the multiply inherited base,
which (refering to the base class) is inherited in a protected way.

RobR
03-19-2002, 05:13 PM
C'mon then, where's my prize??:mad:

Prelude
03-19-2002, 05:57 PM
>C'mon then, where's my prize??
You don't get a prize when you cheat ;)
Though I very much like your taste in books, you could have at least tried putting the answer in your own words. :D

So...when was the last time you used a protected abstract virtual base pure virtual private destructor ?

-Prelude

incognito
03-19-2002, 06:07 PM
I learned something about that from STYC++ in 21 Days.........Haven't really used because I am just starting out........might use it some day though.

RobR
03-20-2002, 01:29 AM
Ok, Ok,


Though I very much like your taste in books, you could have at least tried putting the answer in your own words.

Worse than that I'm afraid......Google search / Cut & paste <hangs head in shame>


So...when was the last time you used a protected abstract virtual base pure virtual private destructor ?

Wouldn't know one if it bit me on the leg:D

(edit) For my penitance(sp) I'll do some research today and post an explanation tonight. That's my real problem - I can usually grasp concepts quite easily, it's sitting down and really coding I have problems with!

RobR
03-20-2002, 03:24 AM
protected abstract virtual base pure virtual private destructor

Destructor - Code called when an object goes out of scope

Private - Can only be called by a member or friend of the class

Pure virtual - A function that contains no code, and can only be used to inherit new classes from. You cannot create objects from a pure virtual function.

So far.....

A pure virtual private destructor is a destructor defined in a class derived from the pure virtual function that can only be called by a member or friend function of the class.

(How'm I doing??)

Virtual Abstract base class - one that contains only pure virtual functions - i.e. at this time we don't know what the object will be, only it's template (ex. vehicle may be an abstract base class 'cos we could use it to create a car, or a bike etc).

Protected - It's implementation is hidden (encapsulated) from us - we can't see the code, we can only derive from it.

So a protected abstract virtual base pure virtual private destructor is a destructor that has to be derived from an implementation-hidden template class and can only be called by a member or friend of the derived class.

Still haven't got the foggiest when I would need to use it, but I would hazard a guess that I don't need to because one will be automatically created for me if I don't specifically implement one.

<PHEW>

Now do I get my reward???:D

Prelude
03-20-2002, 09:36 AM
>How'm I doing??
Considerably better

>Still haven't got the foggiest when I would need to use it
Neither do I, and I've been working with C++ for years.

>Now do I get my reward???
Okay, I was kind of sneaky with that reward concept. You see, I knew that just about everyone ( with the exception of Sorensen perhaps ) had no idea what it was or when it was needed. If someone wanted to answer correctly then they'd have to do quite a bit of research. Your reward is the knowledge you gained while trying to figure it out :D

p.s. Expert C Programming is still a very good investment if you can find it. Too bad it's out of print.

-Prelude

RobR
03-20-2002, 11:20 AM
Tell you what. Lend me your copy, promise I'll let you have it back real soon:D

Prelude
03-20-2002, 11:23 AM
>Lend me your copy, promise I'll let you have it back real soon
I don't lend out my good books, especially the ones that are really hard to find, but I can let you have C by Example if you need a foot rest or something. :D

-Prelude

Unregistered
03-21-2002, 05:12 AM
any more jokes?

ober
03-22-2002, 06:36 AM
When computer programmers are hungry they take mega-bites

Old programmers never die, they just can't C as well

Old programmers never die .. they just lose their memory

Technically speaking a programmer's favorite subject with his
boss is usually arrays

Local Area Network in Australia: the LAN down under

Oh what a tangled web we weave. On the Internet.

lightatdawn
03-22-2002, 10:56 AM
Cant remember where i got this from....

Real Programmers

Real Programmers don't write specs -- users should consider themselves
lucky to get any programs at all and take what they get.

Real Programmers don't comment their code. If it was hard to write, it
should be hard to understand and even harder to modify.

Real Programmers don't write application programs; they program right
down on the bare metal. Application programming is for feebs who can't
do systems programming.

Real Programmers don't eat quiche. In fact, real programmers don't know
how to SPELL quiche. They eat Twinkies, and Szechwan food.

Real Programmers' programs never work right the first time. But if you
throw them on the machine they can be patched into working in "only a
few" 30-hour debugging sessions.

Real Programmers never work 9 to 5. If any real programmers are around
at 9 AM, it's because they were up all night.

Real Programmers don't write in BASIC. Actually, no programmers write
in BASIC, after the age of 12.

Real Programmers don't write in PL/I. PL/I is for programmers who can't
decide whether to write in COBOL or FORTRAN.

Real Programmers don't document. Documentation is for simps who can't
read the listings or the object deck.

Real Programmers only write specs for languages that might run on future
hardware. Noboby trusts them to write specs for anything homo sapiens
will ever be able to fit on a single planet.

Real Programmers spend 70\% of their work day fiddling around and then
get more done in the other 30\% than a user could get done in a week.

Real Programmers are surprised when the odometers in their cars don't
turn from 99999 to 9999A.

Real Programmers are concerned with the aesthetics of their craft; they
will writhe in pain at shabby workmanship in a piece of code.

Real Programmers think they know the answers to your problems, and will
happily tell them to you rather than answer your questions.

Real Programmers never program in COBOL, money is no object.

Real Programmers don't think that they should get paid at all for their
work, but they know that they're worth every penny that they do make.

Real Programmers log in first thing in the morning, last thing before they
go to sleep, and stay logged in for lots of time in between.

Real programmers don't draw flowcharts. Flowcharts are after all, the
illerate's form of documentation.

Real Programmers don't use Macs. Computers which draw cute little
pictures are for wimps.

Real Programmers don't read manuals. Reliance on a reference is the
hallmark of a novice and a coward.

Real Programmers don't write in COBOL. COBOL is for gum chewing twits
who maintain ancient payroll programs.

Real Programmers don't write in FORTRAN. FORTRAN is for wimpy
engineers who wear white socks. The get excited over finite state analysis
and nuclear reactor simulations.

Real Programmers don't write in Modula-2. Modula-2 is for insecure
analretentives who can't choose between Pascal and COBOL.

Real Programmers don't write in APL, unless the whole program can be
written on one line.

Real Programmers don't write in Lisp. Only effeminate programmers use
more parentheses than actual code.

Real Programmers don't write in Pascal, Ada or any of those other pinko
computer science languages. Strong variable typing is for people with
weak memories.

Real Programmers scorn floating point arithmetic. The decimal point was
invented for pansy bedwetters who are unable to think big.

Real Programmers know every nuance of every instruction and use them
all in every Real Program. Some candyass architectures won't allow
EXECUTE instructions to address another EXECUTE instruction as the
target instruction. Real Programmers despise petty restrictions.

Real Programmers don't like the team programming concept. Unless, of
course, they are the Chief Programmer.

Real Programmers have no use for managers. Managers are sometimes
a necessary evil. Managers are good for dealing with personnel bozos,
bean counters, senior planners and other mental defectives.

Real programmers ignore schedules.

Real Programmers don't bring brown bag lunches to work. If the vending
machine sells it, they eat it. If the vending machine doesn't sell it, they
don't eat it.

Real Programmers think better when playing Adventure or Rogue.

Real Programmers use C since it's the easiest language to spell.

Real Programmers don't use symbolic debuggers, who needs symbols.

Real Programmers only curse at inanimate objects.

Deckard
03-22-2002, 11:01 AM
Real Programmers also don't write "User Interfaces". Users have no business interfacing with the professional masterpieces they code. ;)

Esparno
03-22-2002, 01:14 PM
We all know:
C:\DOS\
C:\DOS\RUN\
RUN\DOS\RUN\

well heres my version

C:\DOS
C;\DOS\RUN\
Bad command or filename

:confused: What went wrong!?

Brian
03-22-2002, 01:20 PM
Originally posted by Esparno
We all know:
C:\DOS\
C:\DOS\RUN\
RUN\DOS\RUN\

well heres my version

C:\DOS
C;\DOS\RUN\
Bad command or filename

:confused: What went wrong!?

Erm...right.

Unregistered
03-22-2002, 06:23 PM
Originally posted by Esparno
We all know:
C:\DOS\
C:\DOS\RUN\
RUN\DOS\RUN\

well heres my version

C:\DOS
C;\DOS\RUN\
Bad command or filename

:confused: What went wrong!?
It's C:\DOS\RUN\ (second line your version) and for my jokes:
The top ten signs that your co-worker is a computer hacker

10. You ticked him off once and your next phone bill was $20,000.

9. He's won the Publisher's Clearing House sweepstakes three years running.

8. When asked for his phone number, he gives it in hex.

7. Seems strangely calm whenever the office LAN goes down.

6. Somehow he/she gets HBO on his PC at work.

5. Mumbled, "Oh, puh-leeez" 95 times during the movie "The Net"

4. Massive RRSP contribution made in half-cent increments.

3. Video dating profile lists "public-key encryption" among turn-ons

2. When his computer starts up, you hear, "Good Morning, Mr. President."

1. You hear him murmur, "Let's see you use that Visa card now, jerk."

Top ten signs you bought a bad computer

10. Lower corner of screen has the words "Etch-a-sketch" on it.

9. It's celebrity spokesman is that "Hey Vern!" guy.

8. In order to start it, you need some jumper cables and a friend's car.

7. It's slogan is "Pentium: redefining mathematics".

6. The "quick reference" manual is 120 pages long.

5. Whenever you turn it on, all the dogs in your neighborhood start howling.

4. The screen often displays the message, "Ain't it break time yet?"

3. The manual contains only one sentence: "Good Luck!"

2. The only chip inside is a Dorito.

1. You've decided that your computer is an excellent addition to your fabulous paperweight collection.

You Might Be An Internet Addict If...

You step out of your room and realize that your parents have moved and you don't have a clue as to when it happened.
Your bookmark list takes 15 minutes to go from top to bottom.
Your nightmares are in HTML and GIFS.
You turn off your modem and get this awful empty feeling, like you just pulled the plug on a loved one.
You start introducing yourself as "Jim at net dot com"
Your heart races faster and beats irregularly each time you see a new WWW site address on TV.
You turn on your intercom when leaving the room so you can hear if new e-mail arrives.
Your wife drapes a blond wig over your monitor to remind you of what she looks like.
All of your friends have an @ in their names.
When looking at a web page full of someone else's links, you notice all of them are already highlighted in purple.
Your dog has its own home page.
You can't call your mother... She doesn't have a modem.
You check your mail. It says "no new messages." So you check it again.
Your phone bill is a heavy as a brick.
You write your homework in HTML and give your instructor the URL.
You don't know the sex of three of your closest friends, because they have neutral nicknames and you never bothered to ask.
Your husband tells you that he has had the beard for 2 months
You wake up at 3 a.m. to go to the bathroom and stop and check your e-mail on the way back to bed.
You tell the kids they can't use the computer because "Daddy's got work to do" -- even though you don't have a job.
You buy a Captain Kirk chair with a built-in keyboard and mouse.
Your wife makes a new rule: "The computer cannot come to bed."
You get a tattoo that says "This body best viewed with Netscape 3.0 or higher."
You never have to deal with busy signals when calling your ISP... because you never log off.
The last girl you picked up was only a GIF.
You ask a plumber how much it would cost to replace the chair in front of your computer with a toilet.
Your wife says communication is important in a marriage... so you buy another computer and install a second phone line so the two of you can chat.
As your car crashes through the guardrail on a mountain road, your first instinct is to search for the "back" button.
(I fit everyone one of those)

I'll stop there. I was looking for top ten reasons compilers are female and top ten reasons computers are male but couldn't find them :(

Isometric
03-22-2002, 06:27 PM
That was me. Forgot I cleared my cookies :-(

Isometric
03-22-2002, 06:31 PM
Im sorry but this is too good:
Girlfriend 1.0 software

Last year, my friend upgraded his GirlFriend 3.1 to GirlFriendPlus1.0 (marketing name: Fiancee1.0).

Recently he upgraded Fiancee1.0 to Wife1.0, and it's a memory hogger! It has taken all his space; and Wife1.0 must be running before he can do anything. Although he didn't ask for them, Wife1.0 came with Plug-Ins such as MotherInLaw and BrotherInLaw. These too slow down the system and cause a slow drain on the resources and well-being of the computer.

Some features I'd like to see in the upcoming GirlFriend4.0:

1. A "Don't remind me again" button.

2. Minimize button.

3. Shutdown feature - An install shield feature so that Girlfriend4.0 can be completely uninstalled if so desired (so you don't lose cache and other objects).

I tried running Girlfriend 2.0 with Girlfriend 1.0 still installed; they tried using the same I/O port and conflicted. Then I tried to uninstall Girlfriend 1.0, but it didn't have an uninstall program. I tried to uninstall it by hand, but it put files in my system directory.

Another thing that sucks--in all versions of Girlfriend that I've used is that it is totally "object orientated" and only supports hardware with gold plated contacts.

Bug warning
Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.1 will refuse to install, claiming insufficient resources.

Isometric
03-22-2002, 06:35 PM
I have way too much time on my hands :-)
The Ten Commandments for C Programmers

1. Thou shalt run lint frequently and study its pronouncements with care, for verily its perception and judgement oft exceed thine.

2. Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end.

3. Thou shalt cast all function arguments to the expected type if they are not of that type already, even when thou art convinced that this is unnecessary, lest they take cruel vengeance upon thee when thou least expect it.

4. If thy header files fail to declare the return types of thy library functions, thou shalt declare them thyself with the most meticulous care, lest grievous harm befall thy program.

5. Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''.

6. If a function be advertised to return an error code in the event of difficulties, thou shalt check for that code, yea, even though the checks triple the size of thy code and produce aches in thy typing fingers, for if thou thinkest ``it cannot happen to me'', the gods shall surely punish thee for thy arrogance.

7. Thou shalt study thy libraries and strive not to re-invent them without cause, that thy code may be short and readable and thy days pleasant and productive.

8. Thou shalt make thy program's purpose and structure clear to thy fellow man by using the One True Brace Style, even if thou likest it not, for thy creativity is better used in solving problems than in creating beautiful new impediments to understanding.

9. Thy external identifiers shall be unique in the first six characters, though this harsh discipline be irksome and the years of its necessity stretch before thee seemingly without end, lest thou tear thy hair out and go mad on that fateful day when thou desirest to make thy program run on an old system.

10. Thou shalt foreswear, renounce, and abjure the vile heresy which claimeth that ``All the world's a VAX'', and have no commerce with the benighted heathens who cling to this barbarous belief, that the days of thy program may be long even though the days of thy current machine be short.

-KEN-
03-22-2002, 06:46 PM
>>Real Programmers only curse at inanimate objects.

:D

Well, I curse at people, too...but the amount of times I've cursed at my computer is probably double.

Sorensen
03-22-2002, 07:03 PM
>Real Programmers use C since it's the easiest language to spell.

Maybe, but Real Men (http://www.ee.ryerson.ca:8080/~elf/hack/realmen.html) use FORTRAN.

Pendragon
03-23-2002, 09:58 AM
Top Ten Signs That You Are An Internet Geek
10
When filling out your driver's license application you give your IP address.
9
You no longer ask prospective dates what their sign is, instead your line is "Hi, what's your URL?"
8
Instead of calling you to dinner, your spouse sends email.
7
You're amazed to find out spam is a food.
6
You "ping" people to see if they're awake, "finger" them to find out how they are, and "AYT" them to make sure they're listening to you.
5
You search the Net endlessly hoping to win every silly free T-shirt contest.
4
You introduce your wife as "my lady@home.wife" and refer to your children as "client applications".
3
At social functions you introduce your husband as "my domain server".
2
After winning the office super bowl pool you blurt out, "I feel so "colon-right parentheses!"


..And the number one sign you are an Internet Geek:

1
Two Words: "Pizza's Here!".


And the evolution of a programmer. http://www.cs.bgu.ac.il/~omri/Humor/evolution.html

Pens.

Unregistered
03-23-2002, 11:49 AM
Its frightening how many of these are actually true!

Pendragon
03-23-2002, 03:49 PM
Top Ten reasons that COMPUTERS are Male:

10. They have a lot of data, but are still clueless.

9. A better model is always just around the corner.

8. They look nice and shiny until you bring them home.

7. It is always necessary to have a backup.

6. They'll do whatever you say if you push the right buttons.

5. The best part of having one is the games you can play.

4. In order to get their attention, you have to turn them on.

3. The lights are on, but nobody's home.

2. Big power surges knock them out for the night.

.....and the number one reason that computers are male.......

1. Size does matter





Top Ten reasons that PROGRAM COMPILERS are Female:

10. Picky, Picky, Picky.

9. They hear what you say, but not what you mean.

8. Beauty is only shell deep.

7. When you ask what's wrong, they say "Nothing".

6. Can produce incorrect results with alarming speed.

5. Always turning simple statements into big productions.

4. Smalltalk is important.

3. You do the same thing for years, and suddenly it's wrong.

2. They make you take the garbage out.

....and the number one reason that compilers are Female....

1. Miss a period and they go wild.

:D

Isometric
03-23-2002, 04:02 PM
THATS what I was looking for!!!! Where did you get that Pendragon?

Pendragon
03-23-2002, 04:38 PM
I've found it in a few different places:

http://jupiter.spaceports.com/~humour/jokes-top10.html
http://www.steveandarlyn.com/cphumor.html
http://www.uselessfacts.net/humour/

A search engine would have come up with roughly 900 sites for this joke. ;)