This reminds me of the cartoons which are sprinked throughout
"Smalltalk-80: Bits of History, Words of Advice." No doubt long out
Some of these were
A black frame with a cartoon word bubble saying "OOPS! I just typed
'Processor <- nil.'!"
A plane with the right wing coming off and flames coming out, and the
pilot saying "I think we'd better boot and resume!"
A woman painting a floor with a paint labled "New System" she's
painted herself into a small corner labled "Old System" then she steps
out of the corner, paints it and says "The nice thing about Smalltalk
is that the paint dries instantly!"
And my favorite, a series of pictures on the left word balloons on the right:
"Here we go!"
FLASH "Oh...too bad"
"This out to be better!"
LAD Compiler doe
not understand => ^h,3ep
Class text image
"Oh, I think I know what that is..."
Hey everybody, Smalltalk works!"
On 8/30/06, Robert Dober <firstname.lastname@example.org> wrote:
On 8/30/06, John Carter <email@example.com> wrote:
> Ah me. In a fit of over user friendliness I did a couple of
> the most colossally stupid things in a class.
> I, with head hung in shame, record them here so that...
> * others may avoid them,
> * I remember to avoid them later,
> * writers of obfusticated ruby may benefit.
> a) Name a method the same as something in the Kernel module and then
> forget that you have done so.
> In particular I overrode "puts" in something that didn't inherit from
> IO. OUCH! That really does make printing debugging statements
> b) Put various key Ruby terms (eg. "raise") in alias statements.
> c) Do two or more of these very very dumb things in the same body of code.
This is a chellange, I am sure I can do better or was it worse?
My blog on Ruby