February 06, 2003

Skid 28

situation standby
as the sump moans
i’ve got
myself
in my pocket
though hit “resend”
4573 times
just to get settled
just to get convinced
(having
one
of those "café bustello moments"

that solidifies opinions
that tests piss)
largely occluded
visions of lake scenery
matters of personal import, such as
shoulder blades
hanging there like a calder
(we relax
into blue eyes, into
learning
leaning into the wheel
when national motivation is winnowing, as

oprah’s
geiger
counter
clicks, as the cat…)
the latex concoctions of “the stylist”
as he ribbons by
the wharves
the fraught air of the controversialist
blooming in seven boroughs
toss up palpable, if impressionist, digits
in time,
the dust of satisfactory explosions

Posted by Brian Stefans at February 6, 2003 02:50 PM
Comments

When Batman went home at the end of a night spent fighting crime, he put on a suit and tie and became Bruce Wayne. When Clark Kent saw a news story getting too hot, a phone booth hid his change into Superman. When you're programming, all the variables you juggle around are doing similar tricks as they present one face to you and a totally different one to the machine.

Posted by: Emmett at January 19, 2004 01:34 AM

The Stack is just what it sounds like: a tower of things that starts at the bottom and builds upward as it goes. In our case, the things in the stack are called "Stack Frames" or just "frames". We start with one stack frame at the very bottom, and we build up from there.

Posted by: Morgan at January 19, 2004 01:34 AM

The rest of our conversion follows a similar vein. Instead of going through line by line, let's just compare end results: when the transition is complete, the code that used to read:

Posted by: Randolph at January 19, 2004 01:34 AM

Let's take a moment to reexamine that. What we've done here is create two variables. The first variable is in the Heap, and we're storing data in it. That's the obvious one. But the second variable is a pointer to the first one, and it exists on the Stack. This variable is the one that's really called favoriteNumber, and it's the one we're working with. It is important to remember that there are now two parts to our simple variable, one of which exists in each world. This kind of division is common is C, but omnipresent in Cocoa. When you start making objects, Cocoa makes them all in the Heap because the Stack isn't big enough to hold them. In Cocoa, you deal with objects through pointers everywhere and are actually forbidden from dealing with them directly.

Posted by: Christiana at January 19, 2004 01:35 AM

Let's take a moment to reexamine that. What we've done here is create two variables. The first variable is in the Heap, and we're storing data in it. That's the obvious one. But the second variable is a pointer to the first one, and it exists on the Stack. This variable is the one that's really called favoriteNumber, and it's the one we're working with. It is important to remember that there are now two parts to our simple variable, one of which exists in each world. This kind of division is common is C, but omnipresent in Cocoa. When you start making objects, Cocoa makes them all in the Heap because the Stack isn't big enough to hold them. In Cocoa, you deal with objects through pointers everywhere and are actually forbidden from dealing with them directly.

Posted by: Annanias at January 19, 2004 01:35 AM