Softpanorama (slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-)

C++ Humor

"Fifty years of programming language research, and we end up with C++ ???"    — Richard A. O'Keefe.

"C++: Hard to learn and built to stay that way."

"How C++ is like teenage sex:

1. It is on everyone's mind all the time.
2. Everyone talks about it all the time.
3. Everyone thinks everyone else is doing it.
4. Almost no one is really doing it.
5. The few who are doing it are: A. Doing it poorly. B. Sure it will be better next time. C. Not practising it safely."

"Writing in C or C++ is like running a chain saw with all the safety guards removed,"    — Bob Gray.

"Ever spend a little time reading comp.lang.c++ ? That's really the best place to learn about the number of C++ users looking for a better language."    — R. William Beckwith.

"C(++) is a write-only, high-level assembler language."    — Stefan Van Baelen.

"C++ : Where friends have access to your private members."    — Gavin Russell Baker.

"The great thing about Object Oriented code is that it can make small, simple problems look like large, complex ones."

C++ in Cantonese is pronounced "C ga ga". Need I say more? (Mark Glewwe)

What I hate about your programming language is that it doesn't work like mine does.

• Top 5 reasons to buy a crappy C++ book (Score:1, Redundant) by Amsterdam Vallon (639622) on Thursday February 06, @12:23PM (#5241935)

  5 -- You won't read it anyway   4 -- It comes out of your company's wallet, not yours   3 -- It's the only language left that doesn't try to be "write once, run on any toaster oven"   2 -- You still can't figure out how pointers work   1 -- It's still less crappy than the writing on Slashdot

   

• When your hammer is C++, everything begins to look like a thumb.

              Steve Haflich in alt.lang.design, December 1994

• An old gem: THE PROGRAMMER'S QUICK GUIDE TO THE LANGUAGES
  
  The proliferation of modern programming languages (all of which seem to have stolen countless features from one another) sometimes makes it difficult to remember what language you're currently using. This handy reference is offered as a public service to help programmers who find themselves in such a dilemma.
  
  =====> TASK: Shoot yourself in the foot.
  
  C: You shoot yourself in the foot.
  
  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."
  
  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, you continue with the attempts to shoot yourself anyway because you have no exception-handling capability.
  
  Pascal: The compiler won't let you shoot yourself in the foot.
  
  Ada: After correctly packing 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 you can't because your foot is of the wrong type.
  
  COBOL: Using 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 re-tied.
  
  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 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...
  
  FORTH: Foot in yourself shoot.
  
  Prolog: You tell your program that you want to be shot in the foot. The program figures out how to do it, but the syntax doesn't permit it to explain it to you.
  
  BASIC: Shoot yourself in the foot with a water pistol. On large systems, continue until entire lower body is waterlogged.
  
  Visual Basic: You'll really only _appear_ to have shot yourself in the foot, but you'll have had so much fun doing it that you won't care.
  
  HyperTalk: Put the first bullet of gun into foot left of leg of you. Answer the result.
  
  Motif: You spend days writing a UIL description of your foot, the bullet, its trajectory, and the intricate scrollwork on the ivory handles of the gun. When you finally get around to pulling the trigger, the gun jams.
  
  APL: You shoot yourself in the foot, then spend all day figuring out how to do it in fewer characters.
  
  SNOBOL: If you succeed, shoot yourself in the left foot. If you fail, shoot yourself in the right foot.
  
  Unix:
  % ls
  foot.c foot.h foot.o toe.c toe.o
  % rm * .o
  rm:.o no such file or directory
  % ls
  %
  
  Concurrent Euclid: You shoot yourself in somebody else's foot.
  
  370 JCL: You send your foot down to MIS and include a 400-page document explaining exactly how you want it to be shot. Three years later, your foot comes back deep-fried.
  
  Paradox: Not only can you shoot yourself in the foot, your users can, too.
  
  Access: You try to point the gun at your foot, but it shoots holes in all your Borland distribution diskettes instead.
  
  Revelation: You're sure you're going to be able to shoot yourself in the foot, just as soon as you figure out what all these nifty little bullet-thingies are for.
  
  Assembler: You try to shoot yourself in the foot, only to discover you must first invent the gun, the bullet, the trigger, and your foot.
  
  Modula2: After realizing that you can't actually accomplish anything in this language, you shoot yourself in the head.
  
  CLARION: You tell your computer to create a program for shooting yourself in the foot w

  Read the rest of this comment...

   

• Academic Programmers A Spotters Guide

  Objectionably Oriented

  OO experienced a Road To Damascus situation the moment objects first crossed her mind. From that moment on everything in her life became object oriented and the project never looked back. Or forwards.

  Instead, it kept sending messages to itself asking it what direction it was facing in and would it mind having a look around and send me a message telling me what was there...

  OO thinks in Smalltalk and talks to you in Eiffel or Modula-3; unfortunately she's filled the disk with the compilers for them and instead of getting any real work done she's busy writing papers on holes in the type systems and, like all OOs, is designing her own perfect language.

  The most dangerous OOs are OODB hackers; they inevitably demand a powerful workstation with local disk onto which they'll put a couple of hundred megabytes of unstructured, incoherent pointers all of which point to the number 42; any attempt to read or write it usually results in the network being down for a week at least.

   

• C++ is like teenage sex:
  • It's on everyone's mind all the time.
  • Everyone talks about it all the time.
  • Everyone thinks everyone else is doing it.
  • Almost no one is really doing it.
  • The few who are doing it are
    • doing it poorly;
    • sure it will be better next time;
    • not practicing it safely.

  toilet graffito at the Technion CS department in Haifa, Israel, 1993-11-08 [ornate PS version]

• Humor
  • P & B Learn C++ -=Pointers=-
  • P & B Learn C++ -=Pointers Again=-
     
• Quotes:
  •  "C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, it blows away your whole leg." - Bjarne Stroustrup
  • C++ is like teenage sex: Everybody is talking about it all  the time, only few are really doing it.
  • In C++ only friends can access your private parts
  • When somebody said "We face new debugging challenges with the migration from C to C++ ."
    he really means:  "Damn, now our programs even crash *before* entering the main() function."
     
• Computer songs and poems C++ Writer

C++ writer, C++ writer.
Please sir or madam, will you play my game?
It took me years to write, doesn't have a name.
It's based on a game by Comrade Pazhitnov,
And I need a job,
So I want to be a C++ writer,
C++ writer.
It's a little game about tetrominoes,
And the object is to remove the rows.
Right now, I'm working for the Daily Mail.
It's a steady job,
But I want to be a C++ writer,
C++ writer.
C++ writer, C++ writer.
It's a thousand levels, give or take a few.
I'll be writing more in a week or two.
I could make it longer if you like the style.
I can change it 'round,
And I want to be a C++ writer,
C++ writer.
If you really like it you can have the rights.
It could make a million for you overnight.
If you must return it you can send it here,
But I need a break,
And I want to be a C++ writer,
C++ writer.
C++ writer, C++ writer.
C++ writer, C++ writer.
C++ writer, C++ writer.
C++ writer, C++ writer.
C++ writer...

Todd's Humor Archive Microsoft C++ and Basic Philosophy (fwd)

Newsgroups: rec.humor.funny
From: JDEMELLO@us.oracle.com (Jeff DeMello, Oracle Secure Systems)
Subject: FUN: Microsoft C++
Date: Wed, 28 Jun 95 4:30:06 EDT

Thanks to Rick Wessman.... 
 
an actual bug report 
 
[ This is from a friend at Microsoft ] 
 
Bug #   Status          Title 
5143    ACTIVE          "Build done" signal makes no sound 
---------- ACTIVE - 01/30/95 - MIKEBLAS -------------------- 
 
Visual C++ makes an audible signal when a build completes. When no developer 
is in the room, this signal doesn't make a sound. To reproduce: 
 
1) Start a build. 
2) Leave the room. 
3) Note that the chime does not make a sound. 
 
We should find a way to make the build bell make a sound even if nobody is 
there to hear it. 
 
This philosophical issue may need program management's attention before being 
resolved. 
 
---------- ASSIGNED to MATTHEWT - 01/30/95 - SCOTF --------- 
 
Can we use the telepathy support in Win95 to contact whomever is logged into 
the machine doing the build? Maybe we should just detect when the developer is 
leaving the room and prompt for a phone number where s/he can be reached. 
 
How about disabling leaving the room during a build? 
 
---------- RESOLVED - BY DESIGN - 01/31/95 - MATTHEWT ------ 
---------- ACTIVE - 02/01/95 - MARKLAM --------------------- 
 
Actually, we can't do this either. The problem is that while you're out of the 
room your build is neither finished nor unfinished. It stays in a state of 
flux until you return and collapse the quantum uncertainty by observing it. 
 
Perhaps we could link the build finished event to a cat in a box? 
 
---------- ASSIGNED to HEISENBERG - 02/01/95 - MARKLAM ----- 
---------- RESOLVED - NOT REPRO - 02/03/95 - HEISENBERG ---- 
 
I cannot repro this. I tried standing just outside my door and it made the 
beep. Do I have to go further from my office? Would the mailroom do? 
 
---------- ACTIVE - 02/03/95 - MIKEBLAS -------------------- 
 
The relative position of the mailroom and your office are relatively uncertain 
to me, Doctor. 
 
Please try again: 
 
1) start a build 
2) leave your office 
3) go down the hall 
4) wait until you don't hear the beep 
5) return to note that the build is done 
 
I think this is how I first repro'ed the problem, but I can't remember what I 
was doing to make it happen. 
 
The idea of disabling leaving the room might be the best possible solution, I 
think. When a build starts, the IDE should pop up a message that says "There 
are no more Fritos" or "The kitchen has closed early" or "The bathroom is 
being cleaned" so the developer will not be tempted to get up and wander 
around. 
 
With minimal rebuild in place, we should consider diversions that won't take 
as long to remedy: "You're expecting a phone call" or "Someone will stop by to 
see you soon". 
 
We need to think of messages that are easy to localize for VC++3.0J. 
 
---------- ASSIGNED to MIKEBLAS - 02/13/95 - MARKLAM ------- 
 
To do this we'll need to avoid messages about the bathrooms and vending 
machines for external releases. Perhaps some customer research is needed to 
find out exactly *why* Visual C++ users leave their keyboards. 
 
Some suggestions (including MB_ types) 
Get a drink : 
(i) You're out of coffee 
(i) You're out of tea 
(i)(i) YYoouuvv''ee hhaadd eennoouugghh 
 
Get something to eat : 
(?) You have no food, remember 
/!\ You need to lose weight, fatso. Sit your ass down 
 
Exercise etc : 
(?) Did You Know - sunlight causes skin cancer 
(i) With a Nordik Trak you can get a workout in front of your monitor. 
Call for home delivery 
/!\ I didn't mean that about your weight 
 
See family : 
(i) They already know you love them 
/!\ They'll only want money for something 
/!\ Your in-laws have arrived 
 
Call of nature : 
 
This could be difficult. Consider supplying bed-pan or similar. 
 
---------- ASSIGNED to MIKEBLAS - 02/13/95 - MARKLAM ------- 
---------- ASSIGNED to MIKEBLAS - 02/16/95 - HEISENBERG ---- 
 
I attempted to repro this once more: 
 
I placed my machine in the forest at the edge of the campus. I started a 
'rebuild all' and ran out of the forest towards my mailroom. My build normally 
takes 3 minutes. After 5 minutes I had not heard anything, so I returned to my 
machine. Unfortunately a tree had fallen on it. I had not heard that, either. 
 
 

Selected by Jim Griffith.  MAIL your joke to funny@clari.net.
Attribute the joke's source if at all possible.  A Daemon will auto-reply.

Remember: Always give your jokes a descriptive "Subject:" line. Don't use "joke" or "submission" or "joke submission," please.