From the Wired.com story on the way that Microsoft scooped out Firefly’s vital innards (thanks, for the tip, Tom!), gobbled them up still palpating and alive, and then threw away the husk:
Microsoft said that the company would welcome any constructive suggestions from Firefly community members."When they provide us with some actionable suggestions, we will be looking into them," Miller said.
Presumably Miller didn’t mean that Microsoft actively seeks out ventures that would incur the risk of liability suits; but perhaps they’re so confident, they don’t care whether their programs are actionable.
Posted by AKMA at January 22, 2003 11:12 PM | TrackBackWhen 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: Adlard at January 13, 2004 01:16 AMThat gives us a pretty good starting point to understand a lot more about variables, and that's what we'll be examining next lesson. Those new variable types I promised last lesson will finally make an appearance, and we'll examine a few concepts that we'll use to organize our data into more meaningful structures, a sort of precursor to the objects that Cocoa works with. And we'll delve a little bit more into the fun things we can do by looking at those ever-present bits in a few new ways.
Posted by: Dionise at January 13, 2004 01:16 AMThis is another function provided for dealing with the heap. After you've created some space in the Heap, it's yours until you let go of it. When your program is done using it, you have to explicitly tell the computer that you don't need it anymore or the computer will save it for your future use (or until your program quits, when it knows you won't be needing the memory anymore). The call to simply tells the computer that you had this space, but you're done and the memory can be freed for use by something else later on.
Posted by: Michael at January 13, 2004 01:16 AMBut variables get one benefit people do not
Posted by: Edward at January 13, 2004 09:32 AMThis is another function provided for dealing with the heap. After you've created some space in the Heap, it's yours until you let go of it. When your program is done using it, you have to explicitly tell the computer that you don't need it anymore or the computer will save it for your future use (or until your program quits, when it knows you won't be needing the memory anymore). The call to simply tells the computer that you had this space, but you're done and the memory can be freed for use by something else later on.
Posted by: Timothy at January 13, 2004 09:32 AMBut variables get one benefit people do not
Posted by: Miles at January 13, 2004 09:32 AM