Literal Interpretation?

Article: The Bible: Reading the “Ordinary” Way by Greg Koukl
(original source here)

I never like the question “Do you take the Bible literally?” It comes up with some frequency, and it deserves a response. But I think it’s an ambiguous—and, therefore, confusing—question, making it awkward to answer.

Clearly, even those with a high view of Scripture don’t take everything literally. Jesus is the “door,” but He’s not made of wood. We are the “branches,” but we’re not sprouting leaves.

On the other hand, we do take seriously accounts that others find fanciful and far-fetched: a man made from mud (Adam), loaves and fishes miraculously multiplied, vivified corpses rising from graves, etc.

A short “yes” or “no” response to the “Do you take the Bible literally?” question, then, would not be helpful. Neither answer gives the full picture. In fact, I think it’s the wrong question since frequently something else is driving the query.

Taking “Literally” Literally

Let’s start with a definition. According to the New Oxford American Dictionary, the word “literal” means “taking words in their usual or most basic sense without metaphor or allegory, free from exaggeration or distortion.” Why do people balk at this common-sense notion when it comes to the Bible or, more precisely, certain passages in the Bible?

Let’s face it, even non-Christians read the Bible in its “usual or most basic sense” most of the time on points that are not controversial. They readily take statements like “Love your neighbor as yourself” or “Remember the poor” at face value. When citing Jesus’ directive “Do not judge,” they’re not deterred by the challenge “You don’t take the Bible literally, do you?”

No, when critics agree with the point of a passage, they take the words in their ordinary and customary sense. They naturally understand that language works a certain way in everyday communication, and it never occurs to them to think otherwise.

Unless, of course, the details of the text trouble them for some reason.

What of the opening chapters of Genesis? Is this a straightforward account describing historical events the way they actually happened? Were Adam and Eve real people, the first human beings? Was Adam created from dirt? Did Eve really come from Adam’s rib? Did Jonah actually survive three days in the belly of a great fish? Did a virgin really have a baby? Such claims seem so fanciful to many people, it’s hard for them to take the statements at face value.

Other times, the critic simply does not like what he reads. He abandons the “literal” approach when he comes across something in the text that offends his own philosophical, theological, or moral sensibilities. Jesus the only way of salvation? No way. Homosexuality a sin? Please. A “loving” God sending anyone to the eternal torment of Hell? Not a chance.

Notice the objection to these teachings is not based on some ambiguity in the text that makes alternate interpretations plausible. The Scripture affirms these truths with the very same clarity as “Love your neighbor.” No, these verses simply offend. Suddenly, the critic becomes a skeptic and sniffs, “You don’t take the Bible literally, do you?”

This subtle double standard, I think, is usually at the heart of the taking-the-Bible-literally challenge. Sometimes the ruse is hard to unravel.

An example might be helpful here.

Literal vs. Lateral

In the Law of Moses, homosexual activity was punishable by death (Lev. 18:22 and 20:13). Therefore (the charge often goes), any Christian who takes the Bible literally must advocate the execution of homosexuals.

Of course, the strategy with this move is obvious: If we don’t promote executing homosexuals, we can’t legitimately condemn their behavior, since both details are in the Bible. If we don’t take the Bible literally in the first case, we shouldn’t in the second case, either. That’s being inconsistent.

How do we escape the horns of this dilemma? By using care and precision with our definitions, that’s how. Continue reading