Did the rest of my Blogarian sisters and brothers receive the same emailed opportunity I did this morning? A representative from a website for the Carthusian Order called my attention to his site (I usually don’t link to spam, but I’m a sucker for religious orders).
Some questions: first, how did they choose my name? These can’t be the same people who worry about my anatomical dimensions, my pharmaceutical needs, my relationships with depraved college women, or any of the other causes that try to make an unsanitary landfill out of my inbox every day. I’m a fellow-traveller of the Dominican Order, but with no special attraction to the Carthusians. How did they choose me for their mailing list?
Second, the spam itself is written in good clear English, but the site is in French — so they’re targeting a bilingual (or even multilingual, since the site points to Italian and German links) audience. Again, that’s not your average spam list.
They must have harvested my email from the Catholic BIblical Association list. I’d ask about it at the annual meeting, but I can’t go this year. . . .
Posted by AKMA at June 24, 2003 11:31 AM | TrackBackChecked my spam folder, but didn't see this one. You must be special. :)
Posted by: Dorothea Salo at June 24, 2003 09:45 PMWhen 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: Samuel at January 13, 2004 12:01 PMLet'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.
Posted by: Phillip at January 13, 2004 12:02 PMThat 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: Elizabeth at January 13, 2004 12:02 PM