AKMA’s Random Thoughts

Agreed.... It shouldn't be too terribly difficult.

I wonder if some clever perl and applescript could pull items out of iCal to reformat them.

Hmmmm....

Though I do recall the vCal/iCal in perl folks complaining about a lot of the difficulties in 'proper' time implementation, this might not be too terribly bad if boiled down to the essentials.

(scratches chin)

Just run MT locally, keep your to do list/ calendar in a blog, and point the aggregator at it via a localhost URI

To riff a bit further on Kevin, that was effectively what I was thinking would work well. Write some applescript (or perl) to snag items from the iCal or calendar file. Then use a call to the xml-rpc interface on a MT server to post the entries. Then magically they can show up in an RSS file....

It's a bit crufty, but it might work.

These secret identities serve a variety of purposes, and they help us to understand how variables work. In this lesson, we'll be writing a little less code than we've done in previous articles, but we'll be taking a detailed look at how variables live and work.

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:

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?

Let's take a moment to reexamine that. What we've done here is create two variables. The first variable is in the Heap, and we're storing data in it. That's the obvious one. But the second variable is a pointer to the first one, and it exists on the Stack. This variable is the one that's really called favoriteNumber, and it's the one we're working with. It is important to remember that there are now two parts to our simple variable, one of which exists in each world. This kind of division is common is C, but omnipresent in Cocoa. When you start making objects, Cocoa makes them all in the Heap because the Stack isn't big enough to hold them. In Cocoa, you deal with objects through pointers everywhere and are actually forbidden from dealing with them directly.

Let's take a moment to reexamine that. What we've done here is create two variables. The first variable is in the Heap, and we're storing data in it. That's the obvious one. But the second variable is a pointer to the first one, and it exists on the Stack. This variable is the one that's really called favoriteNumber, and it's the one we're working with. It is important to remember that there are now two parts to our simple variable, one of which exists in each world. This kind of division is common is C, but omnipresent in Cocoa. When you start making objects, Cocoa makes them all in the Heap because the Stack isn't big enough to hold them. In Cocoa, you deal with objects through pointers everywhere and are actually forbidden from dealing with them directly.