03.04.2013 Views

An Introduction to Biblical Hebrew Syntax

An Introduction to Biblical Hebrew Syntax

An Introduction to Biblical Hebrew Syntax

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3a. ערַ ז־ל ֶ֫<br />

ָכּ תא ֵ דבֵּ אַ תְּ וַ<br />

׃ה ָכלָ ְמ ַמּ ה ַ<br />

3b. שׁגֶ ֶנּ֫ ה־ת ַ א ֶ יתִּ דְ בַ אֲ הַ וְ<br />

איהִ ה ַ<br />

She (Athaliah) made destroyed (Piel) the whole royal<br />

seed.<br />

2 Kgs 11:1<br />

I (YHWH) will cause that soul <strong>to</strong> perish (Hiphil).<br />

Lev 23:30<br />

Admittedly, for the sake of “good” English we would probably translate דבא in<br />

both instances ‘destroy,’ but in doing that we would gloss over a fundamental<br />

distinction in <strong>Hebrew</strong>. In the first example, the writer conceptualizes the object, the<br />

royal family, as “accidentally” transferred in<strong>to</strong> the state of perdition, but in the second<br />

example, the lawgiver presents the object, that soul, as an ac<strong>to</strong>r in the event of<br />

perishing. Without the causative notion of the Hiphil, the sentence would read as a<br />

Qal, just as in:<br />

3c.<br />

םתֶּ דְ בַ אֲ ו ַ You will perish (Qal).<br />

Deut 11:17<br />

e Whereas the Piel represents the subject as transposing an object in<strong>to</strong> the state or<br />

condition corresponding <strong>to</strong> the notion expressed by the verbal root, the Hiphil<br />

represents the subject as causing an object <strong>to</strong> participate indirectly as a second subject<br />

in the notion expressed by the verbal root. 6 In fact, this notion probably accounts for<br />

the Hiphil’s distinctive form. The Hiphil stem’s characteristic h preformative, derived<br />

from a thirdperson personal pronoun, reflects a designation of a second subject’s<br />

participation in the action. 7 In E. A. Speiser’s view the Hiphil originally signified: ‘X<br />

(the subject) caused that Y (the second subject) be or do something.’ 8<br />

6<br />

Jenni emphasizes, <strong>to</strong>o, that the Piel tends <strong>to</strong> be habitual, while the Hiphil tends <strong>to</strong><br />

refer <strong>to</strong> occasional or onetime situations; this difference is especially relevant <strong>to</strong> the<br />

participles; Pi˓el, 55–65.<br />

7<br />

“The Semitic personal pronouns for the third person exhibit virtually the same<br />

variations of initial sounds that we have found in the causative prefixes,” i.e., š in,<br />

e.g., Akkadian ~ h in, e.g., <strong>Hebrew</strong>. See E. A. Speiser, “Studies in Semitic<br />

Formatives,” Journal of the American Oriental Society 56 (1936) 22–46, esp. 23–33;<br />

rpt. in his Oriental and <strong>Biblical</strong> Studies, ed. J. J. Finkelstein and Moshe Greenberg<br />

(Philadelphia: University of Pennsylvania, 1967) 403–32, at 409, cited from the<br />

reprint. See 21.1c n. 8. There may be some old causatives in š in <strong>Biblical</strong> <strong>Hebrew</strong> (as<br />

there are š causatives in Aramaic, the result of loans from Akkadian; e.g., <strong>Biblical</strong><br />

Aramaic šêzīb ‘<strong>to</strong> rescue’). On these forms, see J. A. Soggin’s essay “Traces of<br />

<strong>An</strong>cient Causatives in š- Realized as Au<strong>to</strong>nomous Roots in <strong>Biblical</strong> <strong>Hebrew</strong>,” in his<br />

Old Testament and Oriental Studies (Rome: <strong>Biblical</strong> Institute, 1975) 188–202.<br />

8<br />

Speiser proposes: “The phrase ‘A orders (wishes, etc) that B build a house’ was<br />

actually construed as ‘A orders, B builds the house.’ In such asyndetic that-clauses<br />

particular emphasis was needed <strong>to</strong> make clear that a given action was <strong>to</strong> be performed<br />

by someone, or that a given quality was attributed <strong>to</strong> someone or something. The

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!