 |
|
|
[I fixed this Flash file so I'm reposting... here's the original intro... as Derek notes in his comment, the "last guy" is Rafael Barreta-Rivera]
I once made the joke that the Four Horsemen -- the sound poetry group that included Steve McCaffery, Paul Dutton and the late bpNichol (who was the last guy again?) -- would be appearing in NY at my digital poetry event. What I really meant was that these guys -- which I found on a Swedish children's site that I highly recommend for adults -- would be appearing. Click away and be treated to a fabulous sound poetry concert in the tradition of the Ursonate and Meredith Monk, with a touch of Steve Reich's Tehillim. (I don't know why I can't make it bigger...)
Posted by Brian Stefans at July 2, 2003 09:24 AM | TrackBackhey brian;
the last guy was Rafael Barreta-Rivera
derek
Seth Roby graduated in May of 2003 with a double major in English and Computer Science, the Macintosh part of a three-person Macintosh, Linux, and Windows graduating triumvirate.
Posted by: Erasmus at January 18, 2004 08:19 PMThese secret identities serve a variety of purposes, and they help us to understand how variables work. In this lesson, we'll be writing a little less code than we've done in previous articles, but we'll be taking a detailed look at how variables live and work.
Posted by: Venetia at January 18, 2004 08:19 PMInside each stack frame is a slew of useful information. It tells the computer what code is currently executing, where to go next, where to go in the case a return statement is found, and a whole lot of other things that are incredible useful to the computer, but not very useful to you most of the time. One of the things that is useful to you is the part of the frame that keeps track of all the variables you're using. So the first place for a variable to live is on the Stack. This is a very nice place to live, in that all the creation and destruction of space is handled for you as Stack Frames are created and destroyed. You seldom have to worry about making space for the variables on the stack. The only problem is that the variables here only live as long as the stack frame does, which is to say the length of the function those variables are declared in. This is often a fine situation, but when you need to store information for longer than a single function, you are instantly out of luck.
Posted by: Prospero at January 18, 2004 08:19 PMSince the Heap has no definite rules as to where it will create space for you, there must be some way of figuring out where your new space is. And the answer is, simply enough, addressing. When you create new space in the heap to hold your data, you get back an address that tells you where your new space is, so your bits can move in. This address is called a Pointer, and it's really just a hexadecimal number that points to a location in the heap. Since it's really just a number, it can be stored quite nicely into a variable.
Posted by: Eliza at January 18, 2004 08:20 PMNote the new asterisks whenever we reference favoriteNumber, except for that new line right before the return.
Posted by: Josias at January 18, 2004 08:20 PM