13.06.2013 Views

63 Colloquial and Li.. - Ganino.com

63 Colloquial and Li.. - Ganino.com

63 Colloquial and Li.. - Ganino.com

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.

90 wolfgang david cirilo de melo<br />

such cases suus can refer either to the subject of the clause it is in or, as<br />

here, to the subject of the main clause. It is only the context <strong>and</strong> <strong>com</strong>mon<br />

sense which show that the terms the Teloboians are to be told are the terms<br />

of the main clause subject, Amphitruo, <strong>and</strong> not the terms of the envoys<br />

themselves. The contrast between suus <strong>and</strong> eius <strong>com</strong>es out clearly in the<br />

following example:<br />

(35) videtque ipse ad paupertatem protractum esse se<br />

suamque filiam esse adultam virginem,<br />

simul eius matrem suamque uxorem mortuam. (Pl. Trin. 109–11)<br />

He sees that he himself has been reduced to poverty, that his daughter is<br />

a grown-up girl, <strong>and</strong> that at the same time her mother, his wife, has died.<br />

Here the two instances of suam show the connection with the main clause<br />

subject: the first modifies the girl, who is the daughter of the subject, the<br />

second modifies the deceased woman, who was the wife of the subject.<br />

The wife was of course also the daughter’s mother, but since the daughter<br />

is neither subject of the main clause nor subject of the accusative <strong>and</strong><br />

infinitive, the connection between her <strong>and</strong> her mother is established with<br />

eius.<br />

The third context in which suus rather than eius is used has to do with<br />

the original meaning of suus, which seems to have been ‘his own’ rather<br />

than just ‘his’. Thus if speakers want to emphasise the close connection<br />

between two elements, they can use suus non-reflexively. We saw this above<br />

in example (20); the construction is best known in collocations of the type<br />

suum cuique ‘to each his own’. 29<br />

The situation in the Romance languages is somewhat different. Meus<br />

‘my’, tuus ‘your’, noster ‘our’ <strong>and</strong> voster ‘your’ survive in Italian as mio, tuo,<br />

nostro <strong>and</strong> vostro, without any real change in meaning. In the third person,<br />

however, there has been a remarkable change. Latin used to distinguish<br />

between reflexive suus <strong>and</strong> non-reflexive eius. Morphologically, suus is like<br />

the other possessive adjectives, but it is unmarked for number, that is, it<br />

can mean ‘his/her’ as well as ‘their’. Eius is the genitive of is <strong>and</strong> as such it<br />

does not agree with its head noun in case, number <strong>and</strong> gender; it means<br />

29 Because of the close proximity between suus <strong>and</strong> quisque the two sometimes came to be regarded as<br />

a single element, leading to case attraction. E. Löfstedt (1956: ii.114) mentions case attraction of suus<br />

in suae cuique parti (<strong>Li</strong>v. 3.22.6) forsuos cuique parti ‘to each part its own people’, <strong>and</strong> attraction of<br />

quisque in omnia . . . suo quoque loco (Var. R. 1.22.6) foromnia . . . suo quidque loco ‘all . . . each in its<br />

place’. In Plautus the latter type of attraction occurs twice: suo quique [= abl.] loco ‘each in its place’<br />

(Mos. 254, Poen. 1178), in a phrase almost identical to the one in Varro. Some instances without<br />

attraction have interesting patterns of verb agreement: suos quisque visunt ‘eachgoestoseehisown’<br />

with plural verb agreement (Epid. 212, cf. also Rud. 980). With uterque the same occurs: cum amica<br />

sua uterque . . . eatis ‘each of you should go with his girlfriend’, with the verb in the second person<br />

plural <strong>and</strong> the noun modified by a third-person possessive.

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

Saved successfully!

Ooh no, something went wrong!