August 05, 2003

Another "Dreamlife" Ad

Tell me I'm nuts... here's the second "Dreamlife" style ad I've seen today (the first is just below)...

Rachel thinks I'm just seeing things, but I've been looking at how people use letters in other Doubleclick Flash ads, and it's nothing like this kind of naive playful stuff with fades etc. on an orange background.

If you see any others, send them to me! (You can find Flash ads in your browser's Temporary Files folder -- you can't just download them from the page.)

Posted by Brian Stefans at August 5, 2003 03:20 PM | TrackBack
Comments

Call your lawyer. Think of the personal writer's colony you could create on the settlement. Plus one firm or another'd hire you up.. but then you'd be doing flash for da man. Seriously, though -- does the background color not match yours exactly?

Posted by: The English Channel at August 5, 2003 04:24 PM

The rest of our conversion follows a similar vein. Instead of going through line by line, let's just compare end results: when the transition is complete, the code that used to read:

Posted by: Petronella at January 18, 2004 05:04 PM

Since 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: Helen at January 18, 2004 05:05 PM

Each Stack Frame represents a function. The bottom frame is always the main function, and the frames above it are the other functions that main calls. At any given time, the stack can show you the path your code has taken to get to where it is. The top frame represents the function the code is currently executing, and the frame below it is the function that called the current function, and the frame below that represents the function that called the function that called the current function, and so on all the way down to main, which is the starting point of any C program.

Posted by: Juliana at January 18, 2004 05:05 PM

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: Eli at January 18, 2004 05:06 PM

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: Joos at January 18, 2004 05:08 PM