RDFWeb and Friend of a Friend (FOAF): 3 degrees

June 23, 2003

3 degrees

From the oops-I-forgot-to-post-this drafts folder: Microsoft have a new thing called three degrees that may be of interest to FOAF developers and others working on standards-based collaborative tools. Does anyone know whether it's a closed box, or whether there is some prospect of interop with other systems?

Posted by danbri at June 23, 2003 07:25 PM

Comments

Thanks!

Posted by: Flüge Mallorca on January 17, 2004 01:07 PM

pretty interesting point of view.I really like it!

Posted by: fluoxetine on January 18, 2004 05:50 PM

We can see an example of this in our code we've written so far. In each function's block, we declare variables that hold our data. When each function ends, the variables within are disposed of, and the space they were using is given back to the computer to use. The variables live in the blocks of conditionals and loops we write, but they don't cascade into functions we call, because those aren't sub-blocks, but different sections of code entirely. Every variable we've written has a well-defined lifetime of one function.

Posted by: Benjamin on January 20, 2004 07:31 AM

Posted by: Fulk on January 20, 2004 07:32 AM

Earlier I mentioned that variables can live in two different places. We're going to examine these two places one at a time, and we're going to start on the more familiar ground, which is called the Stack. Understanding the stack helps us understand the way programs run, and also helps us understand scope a little better.

Posted by: Juliana on January 20, 2004 07:32 AM

Inside 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: Sybil on January 20, 2004 07:32 AM

Note the new asterisks whenever we reference favoriteNumber, except for that new line right before the return.

Posted by: Warham on January 20, 2004 07:32 AM

When 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: Court on January 20, 2004 07:33 AM

This will allow us to use a few functions we didn't have access to before. These lines are still a mystery for now, but we'll explain them soon. Now we'll start working within the main function, where favoriteNumber is declared and used. The first thing we need to do is change how we declare the variable. Instead of

Posted by: Blaise on January 20, 2004 07:33 AM

That 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: Ottewell on January 20, 2004 07:33 AM

This code should compile and run just fine, and you should see no changes in how the program works. So why did we do all of that?

Posted by: Emma on January 20, 2004 07:33 AM

This code should compile and run just fine, and you should see no changes in how the program works. So why did we do all of that?

Posted by: Silvester on January 20, 2004 07:33 AM

sms sprüche

Posted by: handylogos on January 22, 2004 01:33 PM

Re: Re: <a href=' http://free-girls-sex-usa.prosexhost.com/index2250.html'

Posted by: rgerhgrt on January 24, 2004 04:32 PM