Anonymous C joined in and replied with this 1 month ago, 2 hours later, 2 hours after the original post[^][v]#1,326,847
Humans have to deal with it, and with the millions that pass every year, we can't all do burials. I thought the compost method was interesting but it'd be a huge stressor on any family to know I'm rotting in a pile of leaves for months.
I'll probably specify cremation and just be responsible and simple about it.
Anonymous F joined in and replied with this 1 month ago, 3 hours later, 12 hours after the original post[^][v]#1,326,887
@1,326,848 (Dana !m8XcrP1kmQ)
The cats will take your eyeballs and crows aren't efficient at picking bones clean. Also kungfu guy at the park has evil to vanquish and you'll just be in the way.
In technology, they have this concept called Stack Overflow. When an integer reaches a certain amount, it flips over and goes right to the very opposite side.
So maybe these very intelligent Doctors of Death have the right idea. If you do enough overwhelming damage, maybe it will stack overflow and completely heal the patient back to perfect health.
Anonymous I joined in and replied with this 1 month ago, 3 hours later, 22 hours after the original post[^][v]#1,326,958
@previous (Oatmeal Fucker !BYUc1TwJMU)
*pushes up glasses* Actually, what you are describing is referred to as an integer overflow. A stack overflow refers to a scenario in which a program attempts to utilize more space than has been allocated to it in a section of memory called the stack, resulting in unexpected behavior.
Anonymous J joined in and replied with this 1 month ago, 9 minutes later, 1 day after the original post[^][v]#1,326,971
@1,326,958 (I) > *pushes up glasses* Actually, what you are describing is referred to as an integer overflow. A stack overflow refers to a scenario in which a program attempts to utilize more space than has been allocated to it in a section of memory called the stack, resulting in unexpected behavior.
Akshly, that's a buffer overflow. A stack overflow occurs specifically on the call stack, and happens when you've made one too many nested function calls (e.g. due to infinite recursion) so that there is no space left in memory allocated to the call stack to store associated variables and the return address etc.