There’s one thing you should know about me. I specialize in a very specific type of memory. First in, last out memory.
“You’re talking about the call stack?”
FROM STEVE WOZINAK
THE FOUNDER OF APPLE
“Mr. Jobs has a function he’d like to discuss with you.”
“Like a sorting algorithm?”
We create the class of the object.
We bring the client into that object, and they fill it with their data structures.
“Then you cause infinite recursion and a stack overflow.”
Well… it’s not, memory management speaking, legal.
It throws an Exception.
I think I found a way $home. And this last GOTO; that’s how I get there!
Code seems logical when we write it. It’s only when we compile it that we realize how it has all sorts of errors.
This was the OS’ responsibility! You are not prepared for this.
IS THE LOCATION OF THE DATA
“The deadline’s approaching.”
I have it under source control.
“I’d hate to see its documentation.”
E X C E P T I O N
You musn’t be afraid to think a little more efficient, darling.
⨳, for “contradiciton”
see also: the wikipedia article on this topic