Damien Broderick wrote:
>
> At 05:40 PM 5/19/01 -0400, Eliezer wrote:
>
> >So, Lee, I suppose you would argue that the so-called "if statement" in
> >programming should really be named the "if-and-only-if statement"?
>
> More concisely, that's the "iff statement".
I rather like the idea that the "if statement" technically means that you
*must* execute the statement if the condition holds true, but that you
*can* execute the statement even if the condition doesn't hold true.
> (Not to be confused, I guess, with the rueful "if only" statement, or the
> caustic "dream on" statement.)
my favorite assembly language instructions
HMC - Halt, Melt, and Catch Fire
WCTPC - Write Current Temperature To Program Counter
CBFM - Clear Bit Five Throughout Memory
EAIT - Execute All Instructions Twice
RPF - Reverse Program Flow
CISA - Change Instruction Set Architectures
DAMIT - Transfer Control to Perdition
BBW - Branch Both Ways
CSUE - Circular Shift Until Empty
BLI - Branch if Loop Infinite
DDMWH - Dump Dim Map of Western Hemisphere
IAND - Illogical AND
REMEC - Re-Enact Most Entertaining Crash
TCTOL - Transfer Control To Overhead Lights
CUDA - Crash Unless Debugger Active
-- -- -- -- --
Eliezer S. Yudkowsky http://singinst.org/
Research Fellow, Singularity Institute for Artificial Intelligence
This archive was generated by hypermail 2b30 : Mon May 28 2001 - 10:00:06 MDT