I'll be in Philadelphia on April 10th for this all-guy event... please come if you're in the area, even if you're not a guy.
Presenting:
Craig Dworkin
Kenny Goldsmith
Aaron Levy
Louis Cabri
Darren Wershler-Henry
Brian Kim Stefans
Public Conversation: "Digital Fever: Case Studies in Archiving Art and Poetry"
Event Date: 2003-04-10 / 6:30 pm - 8:30pm
http://slought.org/toc/calendar/display.php?id=1144
Posted by Brian Stefans at April 1, 2003 12:15 AMThis back and forth is an important concept to understand in C programming, especially on the Mac's RISC architecture. Almost every variable you work with can be represented in 32 bits of memory: thirty-two 1s and 0s define the data that a simple variable can hold. There are exceptions, like on the new 64-bit G5s and in the 128-bit world of AltiVec
Posted by: Daniel at January 18, 2004 08:12 PMOur 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.
Posted by: James at January 18, 2004 08:12 PMThe 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.
Posted by: Valentine at January 18, 2004 08:13 PMOur 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.
Posted by: Juliana at January 18, 2004 08:13 PMWhen 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.
Posted by: Wombell at January 18, 2004 08:14 PM