On this one, viewers/readers here might like to think about how similar is this historical (written 1950) co-incidence from Pablo Neruda's poetry--and his is only one of many such critiques that have risen from that 'other' America, or as Neruda also says, from those who have been "amamantado en sangre de su herencia" ("nursed on the blood of your inheritance" ["America I do not call your name without hope"]):

United Fruit Company

When the trumpet blared everything
on earth was prepared
and Jehovah distributed the world
to Coca-Cola Inc., Anaconda,
Ford Motors and other entities:
United Fruit, Inc.
reserved for itself the juiciest,
the central seaboard of my land,
America's sweet waist.
It rebaptized its lands
the "Banana Republics,"
and upon the slumbering corpses,
upon the restless heroes
who conquered renown,
freedom and flags,
it established the comic opera:
it alienated self-destiny,
regaled Caesar's crowns,
unsheathed envy, drew
the dictatorship of flies:
Trujillo flies, Tacho flies,
Carias flies, Martinez flies,
Ubico flies, flies soaked
in humble blood and jam,
drunk flies that drone
over the common graves,
circus flies, clever flies
versed in tyranny.

Among the bloodthirsty flies
the Fruit Company disembarks,
ravaging coffee and fruits
for its ships that spirit away
our submerged lands' treasures
like serving trays.

Meanwhile, in the seaports'
sugary abysses,
Indians collapsed, buried
in the morning mist:
a body rolls down, a nameless
thing, a fallen number,
a bunch of lifeless fruit
dumped in the rubbish heap.

**Translated by Jack Schmitt**

When a variable is finished with it's work, it does not go into retirement, and it is never mentioned again. Variables simply cease to exist, and the thirty-two bits of data that they held is released, so that some other variable may later use them.

Our next line looks familiar, except it starts with an asterisk. Again, we're using the star operator, and noting that this variable we're working with is a pointer. If we didn't, the computer would try to put the results of the right hand side of this statement (which evaluates to 6) into the pointer, overriding the value we need in the pointer, which is an address. This way, the computer knows to put the data not in the pointer, but into the place the pointer points to, which is in the Heap. So after this line, our int is living happily in the Heap, storing a value of 6, and our pointer tells us where that data is living.

To address this issue, we turn to the second place to put variables, which is called the Heap. If you think of the Stack as a high-rise apartment building somewhere, variables as tenets and each level building atop the one before it, then the Heap is the suburban sprawl, every citizen finding a space for herself, each lot a different size and locations that can't be readily predictable. For all the simplicity offered by the Stack, the Heap seems positively chaotic, but the reality is that each just obeys its own rules.

The most basic duality that exists with variables is how the programmer sees them in a totally different way than the computer does. When you're typing away in Project Builder, your variables are normal words smashed together, like software titles from the 80s. You deal with them on this level, moving them around and passing them back and forth.

This code should compile and run just fine, and you should see no changes in how the program works. So why did we do all of that?