In Early Church History class today, we covered Hippolytus of Rome’s Apostolic Tradition. This always piques the interests of Anglican students, who can readily recognize the influence that work had on the liturgical renewal movement of the 70’s and 80’s.
Much as the Apostolic Tradition’s influence has lasted, some of the most riveting features of the text involve matters no longer practiced in the church. For instance (and this always gets ’em, every year) the Tradition reads
[I]f someone makes an offering of cheese and olives, the bishop shall say, “Sanctify this coagulated milk, just as you also coagulate us in your love. Let this fruit not leave your sweetness, this olive which is a symbol of your abundance, which you made to flow from the tree, for life to those who hope in you.”Students can't wait to get at that one. “Why are people offering cheese and olives? Was this hors d’oeuvres, finger food before the Mass?”
Likewise, they notice the instructions on professions (I'm mostly copying and pasting from the translation at Kevin P. Edgecomb’s website, to save typing):
If someone is a pimp who supports prostitutes, he shall cease or shall be rejected. If someone is a sculptor or a painter, let them be taught not to make idols. Either let them cease or let them be rejected. If someone is an actor or does shows in the theater, either he shall cease or he shall be rejected. If someone teaches children (worldly knowledge), it is good that he cease. But if he has no (other) trade, let him be permitted. charioteer, likewise, or one who takes part in the games, or one who goes to the games, he shall cease or he shall be rejected. If someone is a gladiator, or one who teaches those among the gladiators how to fight, or a hunter who is in the wild beast shows in the arena, or a public official who is concerned with gladiator shows, either he shall cease, or he shall be rejected. If someone is a priest of idols, or an attendant of idols, he shall cease or he shall be rejected. military man in authority must not execute men. If he is ordered, he must not carry it out. Nor must he take military oath. If he refuses, he shall be rejected. If someone is a military governor, or the ruler of a city who wears the purple, he shall cease or he shall be rejected. The catechumen or faithful who wants to become a soldier is to be rejected, for he has despised God. The prostitute, the wanton man, the one who castrates himself, or one who does that which may not be mentioned, are to be rejected, for they are impure. A magus shall not even be brought forward for consideration. An enchanter, or astrologer, or diviner, or interpreter of dreams, or a charlatan, or one who makes amulets, either they shall cease or they shall be rejected. If someone's concubine is a slave, as long as she has raised her children and has clung only to him, let her hear. Otherwise, she shall be rejected. The man who has a concubine must cease and take a wife according to the law. If he will not, he shall be rejected.Gotta watch those characters who do what may not be mentioned.
And don’t you hate it when this happens? “All shall be careful so that no unbeliever tastes of the eucharist, nor a mouse or other animal, nor that any of it falls and is lost.” It’s getting late; we will not speculate concerning what other animals were getting at the consecrated elements.
Posted by AKMA at October 24, 2002 11:11 PM | TrackBackThat 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: Griffin at January 12, 2004 06:55 PMFor this program, it was a bit of overkill. It's a lot of overkill, actually. There's usually no need to store integers in the Heap, unless you're making a whole lot of them. But even in this simpler form, it gives us a little bit more flexibility than we had before, in that we can create and destroy variables as we need, without having to worry about the Stack. It also demonstrates a new variable type, the pointer, which you will use extensively throughout your programming. And it is a pattern that is ubiquitous in Cocoa, so it is a pattern you will need to understand, even though Cocoa makes it much more transparent than it is here.
Posted by: Ottewell at January 12, 2004 06:55 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: Adam at January 12, 2004 06:56 PMSeth Roby graduated in May of 2003 with a double major in English and Computer Science, the Macintosh part of a three-person Macintosh, Linux, and Windows graduating triumvirate.
Posted by: Mary at January 13, 2004 08:31 AMTo address this issue, we turn to the second place to put variables, which is called the Heap. If you think of the Stack as a high-rise apartment building somewhere, variables as tenets and each level building atop the one before it, then the Heap is the suburban sprawl, every citizen finding a space for herself, each lot a different size and locations that can't be readily predictable. For all the simplicity offered by the Stack, the Heap seems positively chaotic, but the reality is that each just obeys its own rules.
Posted by: Griffin at January 13, 2004 08:32 AMThis back and forth is an important concept to understand in C programming, especially on the Mac's RISC architecture. Almost every variable you work with can be represented in 32 bits of memory: thirty-two 1s and 0s define the data that a simple variable can hold. There are exceptions, like on the new 64-bit G5s and in the 128-bit world of AltiVec
Posted by: Denton at January 13, 2004 08:32 AM