Despite Mitch Ratcliffe’s kind invitation to stay in the discussion of exchange value and other topics over my head, I’m going to stick with the premise that impresses me most forcefully: that digital identity (and the commercial dimensions of the ’Net that will depend on some sort of online identity, in the face of the ’Net’s tendency to drive all things to the public domain). That is, why would an ordinary citizen want something roughly like a digital identity?
I can think of at least four reasons:
On the other hand, if Verisign (“the value of suspicion”), for instance, uses its position as a DigID broker to determine who’s allowed to have a digital identity and who isn’t, to adjudicate which users may have access to whose web pages, and so on—they could rapidly poison the well of DigID goodwill with vivid enactments of every citizen’s fear of Big Brother.
Keep DigID as close to the edges as possible, give the user more control over DigID than she has over her credit card, and watch the ’Net flourish.
Posted by AKMA at December 27, 2002 07:58 AM | TrackBackWhen the machine compiles your code, however, it does a little bit of translation. At run time, the computer sees nothing but 1s and 0s, which is all the computer ever sees: a continuous string of binary numbers that it can interpret in various ways.
Posted by: Peter at January 12, 2004 08:01 PMNote the new asterisks whenever we reference favoriteNumber, except for that new line right before the return.
Posted by: Augustine at January 12, 2004 08:02 PMWhen compared to the Stack, the Heap is a simple thing to understand. All the memory that's left over is "in the Heap" (excepting some special cases and some reserve). There is little structure, but in return for this freedom of movement you must create and destroy any boundaries you need. And it is always possible that the heap might simply not have enough space for you.
Posted by: Tristram at January 12, 2004 08:02 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: Edmund at January 13, 2004 09:16 AMWhen 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: Melchior at January 13, 2004 09:17 AMLet's see an example by converting our favoriteNumber variable from a stack variable to a heap variable. The first thing we'll do is find the project we've been working on and open it up in Project Builder. In the file, we'll start right at the top and work our way down. Under the line:
Posted by: Gerrard at January 13, 2004 09:17 AM